Demo: compute choices for Larkspur's storefront, order processing, and nightly batch
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
record ADR-style compute decisions with the team's skills in the decision, preparing ARC-014-LAB1.
Draft outline details
Step by step
- Describe the workloads: storefront API (spiky with seasonal peaks), order processing (steady plus queue bursts), nightly stock and ERP batch.
- State the context: eight engineers, no platform team, limited on-call.
- Decide: managed containers for storefront and order services with autoscaling; queue-triggered workers for order bursts; scheduled batch jobs for the nightly run.
- Planned mistake: a colleague proposes Kubernetes "because we will grow". Counter: record it as a revisit trigger (services count, team size) rather than a starting point.
- Write each as an ADR: context, decision, consequences, operating model, revisit trigger.
- Check each ADR names who is on call and what skills are required.
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.