Advanced level · Module 4: Replication, Availability and Recovery · Lesson 3 of 4
Managed and Cloud Databases
Weigh managed database services against running your own server.
In this lesson you will
- Compare self-managed and managed databases
- Evaluate cost, location, connectivity and exit options
Key concepts
managed database serviceshared responsibilitydata locationvendor lock-in
The lesson
Managed services run the database for you: backups, updates, replicas and monitoring are largely handled. You still design the schema, manage access and pay monthly in a foreign currency.
Consider where data is stored and whether that is acceptable to the organisation and its partners, the latency and reliability of the connection from your offices, and costs as data grows.
Plan an exit: can you export your data and move elsewhere? Standard PostgreSQL features keep you portable; proprietary extensions can tie you to one provider.
Step by step
- List the tasks a managed service would take over.
- Estimate monthly costs for two options.
- Check data location and connectivity requirements.
- Write a recommendation with an exit plan.
Practice activity
Write a recommendation for hosting the health database: self-managed, managed or hybrid.
Expected result: A justified recommendation covering cost, responsibility, data location, connectivity and exit.
Check your understanding
-
Under shared responsibility, what remains your job with a managed database?
Show answer
For example schema design, access control and data quality.
-
What is vendor lock-in?
Show answer
Depending on provider-specific features so that moving elsewhere is difficult.
Taught live by an instructor — online or in person. Free course lessons are for self-study and do not lead to a certificate — see registration options.