Deployment architecture
ShardingSphere provides many practical deployment patterns to solve your cases, but this section will introduce the necessary components with an illustrative and simple one.
Applications are the external visitors, and a computing node, a proxy, is in charge of receiving traffic, parsing SQL, and calculating and scheduling distributed tasks. The registry will persist the metadata, rules, configurations, and cluster status. All the databases will become storage nodes persisting the data and running some calculation jobs.
The following diagram shows one of the three possible deployment architectures you can use with ShardingSphere. These are Proxy, Java database connectivity (JDBC), or hybrid, as mentioned in Chapter 1, The Evolution of DBMSs, DBAs, and the Role of Apache ShardingSphere, under the The architecture possibilities at your disposal section:
Figure 2.6 – ShardingSphere-Proxy deployment architecture
If you have...
