Amazon Aurora with PostgreSQL Compatibility is a relational database service that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. We review the functionality in order to understand the architectural differences that contribute to improved scalability, availability, and durability. We also dive deep into the capabilities of the service and review the latest available features. Finally, we walk through the techniques that can be used to migrate to Amazon Aurora.
<Read content on slide>
The purple graphic on this slide is linked to the location of the Ember font family.
http://typography.aka.amazon.com/fonts/1
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Quorum system for read/write; latency tolerant
Quorum membership changes do not stall writes
Y-axis: Recovery time in seconds (less is better)
X-axis: Writes / Second (more is better)
Z-axis / bubble size: amount of redo log which must be recovered.
Test details:
SYSBENCH configured with 250 tables and 450000 rows per table (30 GiB). 1024 clients running from r4.8xlarge in same AZ.
PostgreSQL EBS is configured with an EXT4 file system on a logical volume (LVM2) striped across three (3) 1000 GiB, 20000 IOPS io1 volumes (60k total IOPS)
Test was conducted by issuing a ‘kill -9’ against the database engine measuring the time from engine start to database availability. Recovery time did not account for failure detection.
PostgreSQL redo size is calculated from the start and end points printed in the server log.
Configuration note: Aurora “survivable_cache_mode” was set to off. Enabling “survivable_cache_mode” in version 9.6.3.1.0.7 resulted in 19 second recovery time. This will be fixed in an upcoming release.
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
PostgreSQL: approx. 95 percentile: 183.13ms. STDEV for 20 minute sample, 72.44, Variance 5247
Amazon Aurora: approx. 95 percentile: 64.48ms, STDEV for 20 minute sample, 4.60, Variance 21
Variance reduced by 99.6%
SYSBENCH configured with 250 tables and 450000 rows per table. 1024 clients running from r4.8xlarge in same AZ.
PostgreSQL EBS is configured with an EXT4 file system on a logical volume (LVM2) striped across three (3) 1000 GiB, 20000 IOPS io1 volumes (60k total IOPS)
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Data is replicated 6 times across 3 Availability Zones
Continuous backup to Amazon S3
Continuous monitoring of nodes and disks for repair
10GB segments as unit of repair or hotspot rebalance
Storage volume automatically grows up to 64 TB
Using the AWS Database Migration Service to migrate data to AWS is simple.
(CLICK) Start by spinning up a DMS instance in your AWS environment
(CLICK) Next, from within DMS, connect to both your source and target databases
(CLICK) Choose what data you want to migrate. DMS lets you migrate tables, schemas, or whole databases
Then sit back and let DMS do the rest. (CLICK) It creates the tables, loads the data, and best of all, keeps them synchronized for as long as you need
That replication capability, which keeps the source and target data in sync, allows customers to switch applications (CLICK) over to point to the AWS database at their leisure.DMS eliminates the need for high-stakes extended outages to migrate production data into the cloud. DMS provides a graceful switchover capability.
Using the AWS Database Migration Service to migrate data to AWS is simple.
(CLICK) Start by spinning up a DMS instance in your AWS environment
(CLICK) Next, from within DMS, connect to both your source and target databases
(CLICK) Choose what data you want to migrate. DMS lets you migrate tables, schemas, or whole databases
Then sit back and let DMS do the rest. (CLICK) It creates the tables, loads the data, and best of all, keeps them synchronized for as long as you need
That replication capability, which keeps the source and target data in sync, allows customers to switch applications (CLICK) over to point to the AWS database at their leisure.DMS eliminates the need for high-stakes extended outages to migrate production data into the cloud. DMS provides a graceful switchover capability.
Using the AWS Database Migration Service to migrate data to AWS is simple.
(CLICK) Start by spinning up a DMS instance in your AWS environment
(CLICK) Next, from within DMS, connect to both your source and target databases
(CLICK) Choose what data you want to migrate. DMS lets you migrate tables, schemas, or whole databases
Then sit back and let DMS do the rest. (CLICK) It creates the tables, loads the data, and best of all, keeps them synchronized for as long as you need
That replication capability, which keeps the source and target data in sync, allows customers to switch applications (CLICK) over to point to the AWS database at their leisure.DMS eliminates the need for high-stakes extended outages to migrate production data into the cloud. DMS provides a graceful switchover capability.
Using the AWS Database Migration Service to migrate data to AWS is simple.
(CLICK) Start by spinning up a DMS instance in your AWS environment
(CLICK) Next, from within DMS, connect to both your source and target databases
(CLICK) Choose what data you want to migrate. DMS lets you migrate tables, schemas, or whole databases
Then sit back and let DMS do the rest. (CLICK) It creates the tables, loads the data, and best of all, keeps them synchronized for as long as you need
That replication capability, which keeps the source and target data in sync, allows customers to switch applications (CLICK) over to point to the AWS database at their leisure.DMS eliminates the need for high-stakes extended outages to migrate production data into the cloud. DMS provides a graceful switchover capability.