Our great sponsors
-
shardingsphere
Distributed SQL transaction & query engine for data sharding, scaling, encryption, and more - on any database.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Opposite to what the documentation tells, the full prefix is jdbc:shardingsphere:absolutepath. I've opened a PR to fix the documentation.
The application uses Apache Shardingsphre to route again depending on the data. If the value computed by the API Gateway is correct, the flow stays "in its lane"; if not, it's routed to the correct database, but with a performance penalty as it's outside its lane.
It's always a good idea to check that the design behaves as expected. We can use OpenTelemetry for this. For more information on how to set up OpenTelemetry in such an architecture, please refer to End-to-end tracing with OpenTelemetry.
Related posts
- ShardingSphere 5.3.0 is released: new features and improvements
- ElasticJob 3.0.2 is released including failover optimization, scheduling stability, and Java 19 compatibility
- ShardingSphere 5.2.1 is released — Here are the highlights
- Apache ShardingSphere 5.2.0 is Released!
- ShardingSphere-Proxy Front-End Protocol Troubleshooting Guide and Examples