27. l Productivity
RDS is optimized for productivity:
most admin tasks only take a few clicks.
Faster time to delivery
Up and running in minutes
Free up time for adding business value
Resource cost efficiencies
28. l Productivity
75% of the common admin tasks are
managed by RDS
Provisioning
Database backups
Patching
Performance management
29. l Productivity
Virtually all common MySQL database
features are still available
30. l Productivity
Multiple databases per instance
Standard user accounts
Connect and query using common MySQL tools & drivers
Tune engine parameters
Import export data using standard MySQL tools (mysqldump)
Diagnostics
Native MySQL replication
SSL for encryption over the wire
Monitor metrics
Shell, super user or direct file system access
31.
32.
33.
34.
35.
36.
37.
38.
39.
40. l Productivity
Painless patching
Control maintenance window times
Automatic upgrades for minor versions of MySQL
Major upgrades need to be initiated
41. l Productivity
CloudWatch Monitoring
Included on all RDS databases
Binary log usage, CPU, connections, memory, network
IOPS, latency and throughput for reads and writes
42. l Productivity
Metric alarms
Set custom alarms on all metrics
Send email, trigger programmatic response
Example: CPU utilization over 90% for 10 minutes
43. l Productivity
One click. High availability.
Automated deployment across multiple AZs
Master and standby are kept in sync
Zero admin overhead
44.
45.
46. l Productivity
Automatic fail-over
Instance or AZ failure triggers fail-over to standby
Updates are intact with synchronous writes
Standby promoted to master. New standby.
Additional data durability relative to single AZ deployment
47. l Productivity
Test fail-over
Trigger fail over
Test application response
Programmatic
48. l Productivity
Update durability
Initiated updates occur across availability zones
Standby is updated and promoted to master
Original master is updated
49. l Productivity
Zero admin:
High availability
Automatic failover
Durable updates
One click
50. l Productivity
On demand test databases
Restore snapshot
Restore to point in time
Repeatable test environments
Unit, integration and smoke testing
51. M Case study
Intuit Live Community
Faster release cycles for more agility
Millions of users, seasonal peaks
Run on EC2, RDS and CloudFormation. Multi-AZ.
Hands free recovery with Amazon RDS
Moved from monthly to weekly releases
54. T Performance
Scalable database storage
5Gb to 1Tb of attached storage
Scale on demand
Scale incrementally, but only as much as you need
55. T Performance
Storage is striped
Data striped across multiple volumes
Higher allocated storage stripes across more volumes
Higher throughput with larger instance types
56. T Performance
Vertical resource scaling
Add additional compute capacity
Increase IO with larger instances
Add memory and CPU
57. T Performance
Read Replicas
Scale beyond capacity constraints of a single instance
Asynchronous replication to replicas
Perfect for read-heavy loads and reporting
58. T Performance
Amazon ElastiCache
In-memory cache service
Ideal front end to RDS for read-heavy applications
Low latency
59. T Performance
Replicas vs Caches
Caches are good for low latency access
over a limited dataset
Replicas provide relatively less performance over
a substantially larger dataset
60. M Case study
Flipboard
6 months to deploy a real time, social magazine
5 million users, 2 billion page flips per month
Run on EC2, RDS and ElastiCache. Multi-AZ.
Better response time (milliseconds) and uptime
Complex queries on use and relevance data
61. M Case study
Gumi
Outgrew existing IT environment
Elasticity to respond to peaks; reduce costs.
Run on EC2, RDS.
10 million visitors a day
Reduced time to market through accelerated development
64. 8 Data Protection
Automatic snapshots
Daily database backups
Transaction log backups every 5 minutes
Everything up to final 5 minutes can be recovered
65. 8 Data Protection
Automated backups
Automated point-in-time backups
1 day retention (extendable to 35 days)
On by default. No additional charge.
66. 8 Data Protection
DB Security groups
DB instances are isolated by default
Control access by source IP address or EC2 security group
Specify IP range: 0.0.0.0/0 discouraged!
67. 8 Data Protection
Use a crash recoverable database engine
Use InnoDB (the default!)
Optimized for crash recovery and data durability
MyISAM can result in lost or corrupt data on restore
InnoDB for point in time and snapshot restoration
68. 8 Data Protection
Avoid in-memory or temporary tables
Not flushed to disk
Point in time recovery plays back operations
Operations need to be on committed to disk
69. 8 Data Protection
RDS in the Virtual Private Cloud
Virtual network, bring your own IP addresses
Complete virtual network control: public, private subnets
Includes Multi-AZ (for MySQL and Oracle)
70. 8 Data Protection
Encryption via SSL
RDS generates SSL certificates for each DB instance
Encryption of data between client and DB instance
71. M Case study
Samsung Smarthub
Needed to reduce IT costs and increase flexibility
AWS and Amazon RDS authenticate every request
Delivers apps, content and push notifications
Saved 34M in hardware and maintenance expenses
85% less than running on-premise
73. l
Productivity
T
Performance
8
Data Protection
Bonus
s
Price optimization
74. s Price optimization
Reserved instances
One time, up front payment
Reserve capacity for your DB instance
Discounted hourly rate
Low, medium and high utilization rates