AWS Database Services Overview
By the end of this lesson, you'll be able to:
- Explain why a managed database service takes on operational work a self-managed database requires
- Name the two broad database families this module covers and what each is built around
- Recognize that AWS offers more than one database service because different workloads have genuinely different needs
Prerequisites: Module 4: "Project: Host a Static Website on S3"
Why "just use a database" isn't a real decision
Every application that remembers anything beyond a single request needs a database — somewhere structured to put data so it can be found again later. What Module 3 taught about EC2 versus a fully managed service applies just as directly here: running a database yourself (installing the engine on a server, patching it, configuring backups, monitoring disk space) is real, ongoing operational work. AWS's managed database services take on a meaningful share of that work for you — exactly how much depends on which service, a distinction this module returns to repeatedly.
Two broad families, not one universal database
This module covers two genuinely different database families, each suited to different problems:
- Relational databases — data organized into structured tables with defined columns and relationships between tables, queried with SQL. Amazon RDS and Amazon Aurora, covered in Lessons 2 and 4, are AWS's managed relational options.
- NoSQL databases — a broader category with several different internal shapes; this course focuses on Amazon DynamoDB specifically, a key-value and document-style database built around fast, predictable lookups by a known key rather than flexible ad-hoc queries across relationships.
Lesson 5 comes back to this split directly, once both families have been covered on their own first.
Why AWS offers more than one database service
It would be simpler, on paper, if one database service fit every workload — but real applications have real differences in how they read and write data. A financial system tracking orders and customers benefits from relational integrity (an order genuinely belongs to one customer, and that relationship should be enforced). A system logging billions of small, independent events benefits from a database that can look up one item by a known key extremely quickly, without needing to reason about relationships between rows at all. Neither service is "better" in the abstract — they're built for different access patterns, and choosing between them (Lesson 5's subject) means understanding your own workload's actual shape first.
Exercise
A colleague says "we should just use whichever AWS database is most popular, so we don't have to think about it." Using what this lesson covered, explain in 2–3 sentences why that reasoning skips a real decision, and what question should be asked instead.
Show hint
The right question is about the shape of the data and how it will be accessed, not about popularity.
AWS Database Services Overview Quiz
My Notes
Log in to keep private notes on this lesson.
Questions about this lesson
No questions yet — be the first to ask.
Log in to ask a question about this lesson.
Summary
AWS offers several distinct managed database services rather than one universal database, because relational and NoSQL workloads have genuinely different shapes and needs — this lesson introduces the landscape so the rest of the module can go deep on each option in turn.