- RDS
- RDS Proxy
- Aurora
- Introduction to Aurora
- Aurora Availability
- Fault Tolerance and Durability
- Aurora Replicas
- Aurora Serverless
- Fully managed database proxy for RDS
- Allows apps to pool and share DB connections established with the database
- Improving database efficiency by reducing the stress on database resources (e.g CPU, RAM)and minimize open connections (and timeouts)
- Serverless, autoscaling, highly available (multi-AZ)
- Reduced RDS and Aurora failover time by up 66%
- Supports RDS (MySQL,PostgreSQL, MariaDB, MS SQL Server) and Aurora (MySQL, PostgreSQL)
- No code changes required for most apps
- Enforce IAM authentication for DB, and securely store credentials in AWS Secrets Manager
- RDS proxy is never publicly accessible
- Fully managed Postgres or MySQL compatible database designed by default to scale and fine-tuned to be really fast
- Aurora automatically grows in increments of 10GB, up to 128 TB
- Combines the speed and availability of high-end databases with the simplicity and cost-effectiveness of open source databases
- Aurora can run either MySQL or Postgres compatible engines
- Aurora MYSQL is 5x better performance than traditional MySQL
- Aurora Postgres is 3x better performance than traditional Postgres
- Aurora Costs more than RDS (20% more) but is more efficient
- 6 copies of your data in 3 AZ:
- Needs only 4 out of 6 copies for writes (so if one AZ is down then it is fine)
- Need only 3 out of 6 for reads
- self healing with peer-to-peer replication
- Storage is striped across 100s of volumes
- Automated failover for master happens in less than 30 seconds
- Master + up to 15 Aurora Read Replicas serve reads
-
Aurora Backup and Failover is handled automatically
-
Snapshots of data can be shared with other AWS accounts
-
Storage is self-healing , in that data blocks and disks are continuously scanned for errors and repaired automatically
Amazon Aurora Replicas | Mysql Read Replicas | |
---|---|---|
Number of Replicas | Up to 15 | Up to 5 |
Replication Type | Asynchronous(ms) | Asynchronous (s) |
Performance impact on primary | Low | High |
Act as failover target | Yes (no data loss) | Yes (potentially minutes of data loss) |
Automated failover | Yes | No |
Support for user-defined replication delay | No | Yes |
Support for different data or schema vs primary | No | Yes |
- Aurora except the database will automatically start up, shut down, and scale capacity up or down based on your application's needs
- Apps used a few minutes several times per day or week, eg. low-volume blog site
- pay for database storage and the database capacity and I/O your database consumes while it is active