First page Back Continue Last page Overview Graphics
A DBD::AnyData Case Study
An example from pairNIC:
- Single DB server, replication not available.
- Query volume getting too high.
- Data seldom updated.
- Many client servers.
Notes:
Here is an example where we used DBD::AnyData at pairnic.
We had a database server that we noticed was starting to get a lot of queries. Replication was not yet an option for us, but we needed to reduce the number of queries on the DB server.
Other points working in our favor were that the data being queried was seldom updated, and that the queries were hitting the server from many different clients.