AWS Certified Solutions Architect – ProfessionalDesign for New SolutionsEasy
A media streaming service wants to implement a new feature that allows users to create custom playlists of video content. This feature requires storing user-specific playlist data, which includes video IDs, order, and metadata. The data needs to be highly available, flexible in schema, and support rapid read/write access for millions of users. The service also anticipates frequent schema changes as new features are added to playlists. Which database service is the most appropriate for this use case?
- AAmazon Aurora PostgreSQL.
- BAmazon Redshift.
- CAmazon DynamoDB.
- DAmazon RDS for MySQL.
Show answer & explanationAnswer & explanation
Correct answer: C. Amazon DynamoDB.
Amazon DynamoDB is a fully managed NoSQL database service that provides fast and flexible performance with seamless scalability. Its schema-less design is ideal for flexible and evolving data models like custom playlists, and it can handle rapid read/write access for millions of users with high availability.
Why the other options are wrong
- A. Amazon Aurora PostgreSQL is a relational database. Similar to RDS for MySQL, it offers high performance but its relational nature is less flexible for 'frequent schema changes' and 'flexible in schema' requirements compared to a NoSQL database like DynamoDB.
- B. Amazon Redshift is a data warehousing service, optimized for analytical queries over large datasets, not for high-throughput, low-latency transactional or operational data like user-specific playlists.
- D. Amazon RDS for MySQL is a relational database. While it can store playlist data, its rigid schema and scalability model (vertical scaling or complex sharding) are less ideal for rapid schema changes and the extreme scale of reads/writes required for millions of users compared to DynamoDB.
DynamoDB for User Profile/Playlist Data
Using Amazon DynamoDB to store and manage highly scalable, flexible, and rapidly accessible user-specific data like profiles, preferences, and playlists.
- NoSQL (key-value/document) database.
- Flexible, schema-less data model.
- Supports rapid read/write access at any scale.
- Highly available and durable.
- Ideal for user profiles, session data, and personalized content.
Memory trick: Playlist data: flexible, fast, and scalable, DynamoDB is the choice.