How Amazon Aurora Works | Amazon Aurora Architecture | Cloud Database Architecture
Ғылым және технология
In this video we take a look at Amazon Aurora Architecture and discuss how it works; including detailed descriptions of Amazon Aurora as a Global Database, their multi-master variant, and their "serverless" offering.
To get a complete breakdown of how Amazon Aurora compares to CockroachDB check out this page: www.cockroachlabs.com/compare...
00:00 Basic Architecture of Amazon Aurora
2:15 Distributed Storage Layer
3:20 Quorum Writes in Amazon Aurora
4:55 Limitation of Amazon Aurora
5:14 Scale & Resilience in Amazon Aurora
5:37 Issues with writes in Amazon Aurora (5-10 second downtime for writes)
7:20 Transaction Consistency in Amazon Aurora (by default you're set to "read committed" you can switch that to "serializable")
9:14 Amazon Aurora as a Global Database
10:39 Inconsistent transactions and write latency issues when scaling Amazon Aurora as a global database
11:45 Resilience in Aurora Global Database
13:20 Compliance with data privacy regulations
15:31 Cost of replicating data in Amazon Aurora
16:12 Issues with Amazon Aurora Multi-Master
#AmazonAurora #GlobalDatabase #CloudDatabase
________________________________________________________________________________________________
How global is Amazon Aurora?: www.cockroachlabs.com/blog/ju...
CockroachDB vs Amazon Aurora: • Cloud Database Archite...
Пікірлер: 5
Great walkthrough mate, couldn't stop noticing the bike in the back ground :)
Well articulated, thanks for the vid
Multi region write latency is issue..but same happens in CockroachDb where in "defualt region" config..commit takes more time for multi region setting. Need to understand how writes are better in CockroachDb vs Aurora in multiregion setup.
I think their leveraging the pivot 3’s software defined storage model.
Amazing presentation! One thing I am really annoyed is the limitation of only being able to replicate asynchronously. I really wish there was an option to replicate synchronously. Multi-Master is definitely limited for sure. But from my knowledge, dealing with write conflicts between multiple writers is a very very difficult problem to solve. The fact that multi-master writer feature is available as a managed service I think is great doe. although I am skeptical of how many uses cases exists for a multi-master setup.