The operational cost of another database
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
count the full cost of each extra datastore.
Planned topics
- Run: provisioning, upgrades, patching, capacity planning.
- Protect: backup and restore tested, security, access control, encryption.
- Observe: monitoring, alerts, dashboards, on-call runbooks.
- People: skills, hiring, on-call burden.
- Data: sync with the source of truth, reindex or rebuild, consistency bugs, extra failure modes.
- Cost scales with the number of different stores, not only the size of data.
Draft outline details
Demonstration
checklist: backup tested, monitoring in place, runbook written, two engineers can operate it, sync strategy defined.
Check your understanding
Which hidden cost appears when data lives in two stores?
Show answer
Keeping them in sync and handling divergence.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.