Rds cross region latency issue

Question

We have an rds instance in us-east-1, the applications that access the rds are in us-east-1 and us-east-2. the two regions have vpc peering. we are load balancing the request received by using route53 weighted routing policy. we are experiencing 10 ms delay when communicating across regions. currently, these 10 ms delays are acceptable between microservices. but when the applications in region2 are accessing rds, we are facing a considerable delay. (due to the large amount of database calls of hibernate ). Are there any was to reduce this database latency ?

Rodney Lester · Answer

"Single digit ms" latency is the design of availability zones, not regions. While us-east-2 and us-east-1 are closer than other regions in the US, it is highly likely the latency will exceed 10 ms. See https://aws.amazon.com/about-aws/global-infrastructure/regions_az/

Joao Rito · Answer

The best method to lower latency when accessing RDS between two regions, in my opinion, would be to set up an RDS read replica in the US-East-2 region. Applications in that area could access the database locally for reads, and query latency would be greatly decreased.

If you must use the US-East-1 region's primary database for writes, do so, however, cross-region traffic will increase write latency. 
The best choice for write-dominant applications in Region 2 would be Aurora Global Database, which provides high-performance inter-region replication, enabling writes in each region and quick, low-latency local reads.

See More: 
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html

Rds cross region latency issue

Añade tu respuesta

Contenido relevante