Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AWS re:Invent re:Cap - 새로운 관계형 데이터베이스 엔진: Amazon Aurora - 양승도

2,168 views

Published on

AWS re:Invent re:Cap 행사에서 발표된 강연 자료입니다. 아마존 웹서비스의 양승도 솔루션스 아키텍트가 발표한 내용입니다.

내용 요약: re:Invent에서 새로 발표된 Amazon Aurora는 My-SQL과 호환되는 관계형 데이터베이스 엔진으로, 상용 고급 데이터베이스의 속도 및 가용성과 오픈소스 데이터베이스의 간편함 및 비용효율성을 모두 갖춘 서비스입니다. 이 세션에서는 MySQL과 Oracle, Microsoft SQL Server, PostgreSQL에 이어 Amazon RDS로 구동되는 다섯 번째 데이터베이스 엔진 Amazon Aurora의 특징과 이점에 대해 소개하도록 하겠습니다.

Published in: Technology
  • Be the first to comment

AWS re:Invent re:Cap - 새로운 관계형 데이터베이스 엔진: Amazon Aurora - 양승도

  1. 1. © 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:
  2. 2. SQL Transactions Caching Logging
  3. 3. SQL Transactions Caching Logging SQL Transactions Caching Logging Application
  4. 4. SQL Transactions Caching Logging SQL Transactions Caching Logging Application
  5. 5. SQL Transactions Caching Logging SQL Transactions Caching Logging Storage Application
  6. 6. 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
  7. 7. Logging + Storage SQL Transactions Caching Control Plane Data Plane Amazon S3 DynamoDB Amazon SWF Amazon Route 53
  8. 8. SQL Transactions AZ 1 AZ 2 AZ 3 Caching Amazon S3
  9. 9. 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
  10. 10. SQL Transactions Caching SQL Transactions Caching SQL Transactions Caching Caching process is outside the DB process and remains warm across a database restart
  11. 11. 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
  12. 12. - 10 20 30 40 50 60 70 10 100 1,000 10,000 Thousands of Writes Per Second 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
  13. 13. - 20 40 60 80 100 120 50 500 5,000 Thousands of Writes per Second 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
  14. 14. - 50 100 150 200 250 300 350 400 100/0 50/50 0/100 Thousands of Operations/Second 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
  15. 15. 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 Replica Lag in milliseconds 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
  16. 16. 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

×