1. Amazon RDS
Nguyen Trung Thanh
LOGO
1

2. Outline
 Concept
 RDS Features, Functionality
 Scalability
 Compare to SQL Azure
 Conclusion
 Q&A
2

3. Solution for Database
Build your own
 For example - MySQL on EC2, Postgres , …
 Acquire instances
 Install the database according to your architecture
 Self manage your database
 Database-as-a-Service
 For example - Amazon RDS,
Xeround, Azure SQL…. ,
3

4. Amazon RDS
RDS = Relational Data Storage
 A Service make it easy to
+ Set up
+ Operate
+ Scale
Relational Database on Cloud
4

5. Elasticity
5

6. Similarities
Web
Portal
Your
App
Change Connection String
6

7. RDS Features, Functionalities
Pre-configured Parameters
Monitoring and Metrics
Automatic Software Patching
Automated Backups
DB Snapshots
Push-Button Scaling
Automatic Host Replacement
Replication: two features
Multi-AZ Deployment, Read Replica
7

8. Amazon RDS Tooling
 MySQL WorkBench
 All the Oracle Tools
 AWS Management Console
 CLI ( Command Line Interface )
 APIs
8

9. Scalability-Two Types of Scaling
9

10. Scalability – Scale Up vs. Scale Out
 Scale Up/Vertical Scaling
 Select next available configuration (EC2, RDS)
 Relatively simple but limited scalability
 Scale Out/Horizontal Scaling
 Add additional resources
 Complicated but high scalability
 RDS Read replicas
10

11. Amazon RDS Scale Up
11

12. Shared Everything vs. Shared Nothing
 Shared Everything
 Scale throughput but limited due to shared resources
 Storage and networking limitations in the cloud
 ScaleDB
 Shared Nothing
 Horizontal data partition / sharding
 Unlimited scalability
 Many design and implementation
challenges
12

13. Stategies for scaling
Read Replicas
Read replicas, also known as master-slave
deployments.
A good option for applications with a high read to write ratio.
A single master database is responsible for handling all writes.
The writes are then replicated to the slaves which are designated
to handle just reads.
Partioning/Sharding
Breaking a larger database up into smaller databases
+ Splitting tables that are not joined in the same query onto different
hosts
+ Duplicating a table across multiple hosts and then splitting where
a row goes.
13

14. Read Replicas
Load Balancer
Master
R R
R
R R
14

15. Read Replicas
15

16. Multi-AZ Deployement
Availability Zones: are distinct locations within
a Region that are engineered to be isolated from
failures in other Availability Zones.
Run a DB Instance as a Multi-AZ
deployment, the “primary” serves database
writes and reads. Amazon RDS provisions and
maintains a “standby” behind the scenes, which
is an up-to-date replica of the primary. The
standby is “promoted” in failover scenarios. After
failover, the standby becomes the primary and
accepts your database operations.
16

17. Multi-AZ Deployement
Double the price
17

18. Sharding
18

19. ScaleBase-Auto Sharding
19

20. Compare to SQL Azure
Amazon RDS
Less Cloudy
Built on MySQL/Oracle
Amazon RDS wins Scale Up
SQL Azure
More Cloudy
Built on SQL Server
SQL Azure wins Scale Out
20

21. Pricing
21

22. Main Amazon RDS Pricing - MySQL
22

23. Main SQL Azure Pricing
23

24. 24

25. 25

26. Conclusion
Simple to Deploy
Managed
Compatible
Scalable
Reliable
Designed for use with other Amazon Web
Services
Secure
Inexpensive: On-Demand DB Instances, Reserved DB
Instances
26

27. Q&A
27