An existing application depends on MySQL-specific SQL, stored procedures, and drivers.
Move to a managed relational database with Multi-AZ availability and read scaling while minimizing application changes.
Which database is most appropriate?
Choose MySQL-Compatible Amazon Aurora to retain compatibility while gaining managed availability and read replicas.
Detailed explanation
The PostgreSQL-compatible engine does not run MySQL-specific SQL and procedures unchanged in all cases.
The PostgreSQL-compatible engine does not run MySQL-specific SQL and procedures unchanged in all cases.
DynamoDB is a nonrelational key-value and document database and does not provide transparent compatibility with the existing SQL.
DynamoDB is a nonrelational key-value and document database and does not provide transparent compatibility with the existing SQL.
Redshift is an analytical data warehouse rather than a general OLTP migration target.
Redshift is an analytical data warehouse rather than a general OLTP migration target.
Aurora MySQL-Compatible preserves MySQL compatibility while providing managed availability and read replicas.
Aurora MySQL-Compatible preserves MySQL compatibility while providing managed availability and read replicas.
Check official documentation
Compare the following points with the official documentation.
Amazon Aurora MySQL-Compatibleの互換性、可用性、レプリカの公式説明を確認する。
Official references
What to confirm
エンジン互換性、ワークロード種別、可用性、読み取りスケールを同時に評価できる。
Key points
- Aurora MySQL-Compatible
- MySQL compatibility
- OLTP
Notes
- Environment:
- Confirm current behavior in the official SAA-C03 guide and AWS service documentation.
Foundation review
Compatibility and migration cost
Changing database engines can increase the amount of SQL and application rewriting.
Workload characteristics
Use a transaction-oriented engine rather than an analytical warehouse for OLTP.