> Due to Amazon Aurora’s unique storage architecture, replication lag is extremely low, typically between 10 ms and 20 ms.
I think in the original announcement, this number was lower, but this is still great.
In this range of latency, the most compelling thing relevant to my needs is the possibility of using read replicas for serving read-only API calls, with minimal risk of having a write API call immediately followed by a read API call serving stale data. It's possible to orchestrate a prevention for that with regular latency-prone MySQL replication, but it carries tremendous complexity depending on the application.
Would be very interested if anyone else has explored this idea further with Aurora.
I think in the original announcement, this number was lower, but this is still great.
In this range of latency, the most compelling thing relevant to my needs is the possibility of using read replicas for serving read-only API calls, with minimal risk of having a write API call immediately followed by a read API call serving stale data. It's possible to orchestrate a prevention for that with regular latency-prone MySQL replication, but it carries tremendous complexity depending on the application.
Would be very interested if anyone else has explored this idea further with Aurora.