A lot of databases claim to have ‘global’ capabilities, including Amazon Aurora. Understanding what your database provider means when they say their database is truly ‘global’ is crucial. If you’re evaluating Aurora, or other products that promise global capabilities, they should have, at the bare minimum, these three requirements:
- Global availability: Leverages geographic diversity of nodes to keep data available. It should be always on and resilient to facility failures and natural disasters.
- Global performance: Supports policies to replicate data close to where it is most often accessed (reads & writes) to achieve optimal global latencies.
- Global consistency: Maintains consistency even in a globally dispersed deployment.
Learn more in the guide about why these three features are crucial, and what they mean for your database performance.