#Aurora postgresql plus

Once we have an Aurora database cluster, adding the first secondary AWS region will automatically turn it into an Aurora Global Database. Geographically it is easy to group the seven (and more to come in the future) overseas markets into less than five AWS regions.

#Aurora postgresql plus

Plus the scalability and availability improvement (think about cross-region failover), migrating to Aurora Global Database is a no-brainer. As for the number of replicas, it will allow us 15 replicas in the primary region and 16 in each secondary region (source). It supports cross-region read-only replicas in up to five AWS regions (secondary regions as named in AWS docs, as opposed to the primary region where the master database instance resides,) with less than one second cross-region replication latency. minimize the impact to the live system.ДЇor the first requirement, AWS Aurora Global Database is a low-hanging fruit solution.

The daily traffic could amount to 20 million accesses, any downtime has impact on real users, any read downtime could result in business loss. The system has been running on production for nearly 2.5 years, now serving eight client systems from seven countries. With the fourth overseas marketвЂ™s rollout date approaching, the fifth, sixth and the seventh overseas market also had their rollout plan laid out. ( source ) How and How NotДЄn architectural level change to address the database replica limit is unavoidable. RDS only supports up to five replicas, no matter same- or cross-region. The fourth is supposed to come early next year, when we hit a wall: In each overseas market, one replica was created to serve that marketвЂ™s API read traffic.ДЄs time went by, the system has been rolled out to three overseas markets. In the main marketвЂ™s AWS region, the master instance serves write traffic coming from importing upstream data and admin applications, one replica serves in-region API read traffic, while another replica serves all regionsвЂ™ batch read traffic. Since Aurora PostgreSQL didnвЂ™t came into being until right before the project start, the database solution was designed to use RDS PostgreSQL with same- and cross-region replicas. The database choice was PostgreSQL and the whole infrastructure is on AWS. In the summer of 2017, we started to design and build a system that imports and administrates business data in the main business region, then ships the data as a suite of microservice API endpoints and batch file feeds to the global markets. This is a story about rescuing a not-so-old system from the legacy architecture design which no longer suits its global requirements.

Migrate PostgreSQL on AWS from RDS to Aurora