sub‐query (see pagination for more details), but also sub‐query with the same mode. No matter how many layers are nested, ShardingSphere can parse to the first sub‐query that contains data table. Once it finds

limitation and an‐ alyze, QoS and observability). • Pluggable: Leveraging the micro kernel and 3 layers pluggable mode, features and database ecosystem can be embedded flexibily. Developers can customize

limitation and an‐ alyze, QoS and observability). • Pluggable: Leveraging the micro kernel and 3 layers pluggable mode, features and database ecosystem can be embedded flexibily. Developers can customize

database function ecology The pluggable architecture of Apache ShardingSphere is composed of three layers ‐ L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer. L1 Kernel Layer An abstraction of

database function ecology The pluggable architecture of Apache ShardingSphere is composed of three layers ‐ L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer. 1.2. Design Philosophy 4 Apache ShardingSphere

limitation and an‐ alyze, QoS and observability). • Pluggable: Leveraging the micro kernel and 3 layers pluggable mode, features and database ecosystem can be embedded flexibily. Developers can customize

database function ecology The pluggable architecture of Apache ShardingSphere is composed of three layers ‐ L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer. 2.1. Connect: Create database upper

database function ecology The pluggable architecture of Apache ShardingSphere is composed of three layers ‐ L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer. 2.1. Connect: Create database upper