Order processing requires MySQL-compatible SQL and ACID transactions with high write throughput.
The database must span Availability Zones and scale storage automatically.
Which data store is most appropriate?
Choose Amazon Aurora for compatible SQL, managed relational transactions, distributed storage, and high availability.
Detailed explanation
S3 stores objects and does not provide transactional row updates.
S3 stores objects and does not provide transactional row updates.
DynamoDB scales key access but does not provide the same relational constraints and SQL model.
DynamoDB scales key access but does not provide the same relational constraints and SQL model.
OpenSearch is a search and analytics engine, not the primary ACID order database.
OpenSearch is a search and analytics engine, not the primary ACID order database.
Aurora provides MySQL or PostgreSQL compatibility, transactions, distributed storage, and Multi-AZ availability.
Aurora provides MySQL or PostgreSQL compatibility, transactions, distributed storage, and Multi-AZ availability.
Check official documentation
Compare the following points with the official documentation.
Amazon Auroraの互換性、ストレージ、レプリケーション、Multi-AZの公式説明を確認する。
What to confirm
Aurora・NoSQL・検索・オブジェクト保存の適用範囲を区別できる。
Key points
- Aurora
- ACID
- Multi-AZ
- Storage scaling
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Relational boundary
Foreign keys, joins, and transactional constraints distinguish this workload from key-value access.
Availability and scale
Write capacity, read replicas, failover time, and storage growth are separate design dimensions.