© 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.

December 8, 2014 | Korea

Amazon Aurora

Re-imagining the Relational Database

양승도 솔루션스 아키텍트

re:

SQL

Transactions

Caching

Logging

SQL

Transactions

Caching

Logging

SQL

Transactions

Caching

Logging

Application

SQL

Transactions

Caching

Logging

SQL

Transactions

Caching

Logging

Application

SQL

Transactions

Caching

Logging

SQL

Transactions

Caching

Logging

Storage

Application

Performance and Scalability

High Throughput with Low Jitter

Push-button Compute Scaling

Storage Auto-scaling

Amazon Aurora Replicas

Reliability

Instance Monitoring and Repair

Fault-tolerant and Self-healing Storage

Automatic, Continuous, Incremental Backups and Point-in-time Restore

Database Snapshots

Security

Encryption at Rest and in Transit

Network isolation

Resource-level Permissions

Manageability

Easy to Use

Easy Migration

Monitoring and Metrics

Automatic Software Patching

DB Event Notifications

Cost-effectiveness Pay Only for What You Use

Logging + Storage

SQL

Transactions

Caching

Control Plane Data Plane

Amazon S3

DynamoDB

Amazon SWF

Amazon Route 53

SQL

Transactions

AZ 1 AZ 2 AZ 3

Caching

Amazon S3

Checkpointed Data Redo Log

Crash at T0 requires

a re-application of the

SQL in the redo log since

last checkpoint

T0 T0

Crash at T0 will result in redo

logs being applied to each segment

on demand, in parallel, asynchronously

SQL

Transactions

Caching

SQL

Transactions

Caching

SQL

Transactions

Caching

Caching process is outside the DB process

and remains warm across a database restart

Page cache

invalidation

Aurora Master

30% Read

70% Write

Aurora Replica

100% New Reads

Shared Multi-AZ Storage

MySQL Master

30% Read

70% Write

MySQL Replica

30% New Reads

70% Write

Single threaded

binlog apply

Data Volume Data Volume

-

10

20

30

40

50

60

70

10 100 1,000 10,000

Th

ou

san

ds o

f W

rite

s P

er

Seco

nd

Number of Tables

Write Performance & Table Count

Aurora

MySQL on I2.8XL

MySQL on I2.8XL with RAM Disk

RDS MySQL with 30,000 IOPS (Single AZ)

Tables Aurora

MySQL

I2.8XL

Local SSD

MySQL

I2.8XL

RAM Disk

RDS MySQL

30K IOPS

(Single AZ)

10 60,000 18,000 22,000 25,000

100 66,000 19,000 24,000 23,000

1,000 64,000 7,000 18,000 8,000

10,000 54,000 4,000 8,000 5,000

-

20

40

60

80

100

120

50 500 5,000

Th

ou

san

ds o

f W

rite

s p

er

Seco

nd

Concurrent Connections

Write Performance & Concurrency

Aurora

RDS MySQL with 30,000 IOPS (Single AZ)

Connections Aurora

RDS MySQL

30K IOPS

(Single AZ)

50 40,000 10,000

500 71,000 21,000

5,000 110,000 13,000

-

50

100

150

200

250

300

350

400

100/0 50/50 0/100

Th

ou

san

ds o

f O

pera

tio

ns/S

eco

nd

Read/Write Ratio

Performance with Query Cache On & Off

Aurora without Caching

Aurora with Caching

RDS MySQL;30,000 IOPS (Single AZ) - without caching

RDS MySQL;30,000 IOPS (Single AZ) - with caching

R/W Ratio

Aurora

Without

Caching

Aurora

With

Caching

RDS MySQL

30K IOPS

Without

Caching

RDS MySQL

30K IOPS

With

Caching

100/0 160,000 375,000 35,000 19,000

50/50 130,000 93,000 24,000 20,000

0/100 64,000 64,000 16,000 16,000

2.6 3.4 3.9 5.4

1,000 2,000 5,000 10,000

0

50,000

100,000

150,000

200,000

250,000

300,000

350,000

Updates per Second

Read

Rep

lica L

ag

in

milliseco

nd

s

Read Replica Lag

Aurora

RDS MySQL;30,000 IOPS (Single AZ)

Updates/

Second Aurora

RDS MySQL

30K IOPS

(Single AZ)

1,000 2.62ms 0s

2,000 3.42ms 1s

5,000 3.94ms 60s

10,000 5.38ms 300s

vCPU Mem Hourly Price

db.r3.large 2 15.25 $0.29

db.r3.xlarge 4 30.5 $0.58

db.r3.2xlarge 8 61 $1.16

db.r3.4xlarge 16 122 $2.32

db.r3.8xlarge 32 244 $4.64

• Storage consumed, up to 64TB, is $0.10/GB/month

• IOs consumed are billed at $0.20 per million IO

• Prices are for Virginia