How to distribute a unique database already in production?
- by JVerstry
Let's assume a successful web spring application running on a MySql or PostGre kind of database. The traffic is becoming so high and the amount of data is becoming so big that a distributed dataase solution needs to be implemented. It is a scalability issue.
Let's assume this application is using Hibernate and the data access layer is cleanly separated with DAO objects.
What would be the best strategy to scale this database? Does anyone have hands on experience to share? Is it possible to minimize sharding code (Shard) in the application?
Ideally, one should be able to add or remove databases easily. A failback solution is welcome too.
I am not looking for you could go for sharding or you could go no sql kind of answers. I am looking for deeper answers from people with experience.