A key benefit of cloud database services is the ability to launch a database in multiple regions with just a few clicks. Typically you’d use a global deployment to enable fast cross-region disaster recovery and to place the data close to your users for fast local performance. A global deployment brings up questions such as: how many regions do I need? What RPO and RTO should I aim for? How do I design a scalable global application? In this session, we’ll discuss tradeoffs to consider for workloads with a global footprint such as financial, travel, or gaming applications, using Amazon Aurora Global Database as an example. You can use these strategies for other MySQL- or PostgreSQL-based cloud services if they have similar capabilities.
Video Stream
