Demo: Larkspur's data stores and their failover design
On This Lesson 3 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
design Larkspur's data platform and flag RPO/RTO gaps for ARC-016-LAB1.
Draft outline details
Step by step
- List workloads: orders and payments records, inventory, product catalog, sessions and carts, product search, reporting.
- Choose: managed relational with multi-AZ for orders and inventory; document or key-value store for carts; cache for catalog reads; managed search for product search; read replica for reporting.
- Set failover and backup per store with PITR windows and cross-region snapshot copies.
- Planned mistake: assuming managed multi-AZ equals DR. Fix: add cross-region snapshot copy and a restore runbook; note the region-loss RTO is hours, not minutes.
- Compare each store's RPO/RTO with the requirements; flag the gap on search (rebuilt from the source, so RPO is nil but rebuild time is long).
- Add the web shop database migration approach: replication-based with a rehearsed cutover.
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.