We have a solution which is spread globally across a few Sybase DB servers and fronted by an Oracle Coherence cache.
Now, we need to support ‘cache speed writes’, yet due to the internationally-replicated nature of our DB, we need to accept data for DB persisting faster than the DB can actually write the data, which you will probably all agree is quite a problem.
I am therefore wondering what the recommended approach to tackle this situation would be.
Points of note:
- There are no constraints
- There are multiple shards split according to usage statistics
I have decided to use horizontal partitioning on some of the larger and more frequently accessed tables, which is something that is natively supported by Sybase ASE 15+ and is transparent to client applications.