Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Best practice of using Sharding-Proxy for different business systems
See original GitHub issueFor different business systems, is it better to deploy a unified Sharding-Proxy or individual Proxy for each business system?
If it is designed to deploy a unified Sharding-Proxy, I’m suprised that some configs such as query.with.cipher.column are global.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
The Next Evolution of the Database Sharding Architecture
One of the best techniques for this is to split the data into separate rows and columns. This splitting of large database tables...
Read more >Oracle Sharding MAA Best Practices
All shard catalog standby databases should use Active Data Guard for the best data protection, and they should reside on separate hardware and...
Read more >What is MongoDB Sharding and the Best Practices? - Geekflare
Another good idea is to monitor your traffic patterns and run the shard balancer only at low-traffic times. As I already mentioned, rebalancing...
Read more >How sharding a database can make it faster
First, partition the historical data into the new database sharding cluster through a sharding algorithm. A program to automatically move data ...
Read more >Database Sharding - Devopedia
The cluster proxy looks at a query and the configuration to know which shard to hit. If shards are large, each shard may...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m familiar with few config.
Maybe at least we can consider letting
query.with.cipher.columnbe configured on every table (for both Sharding-JDBC and Sharding-Proxy) ?The migration process of data masking of some tables should not affect other tables that have been using data masking.