CompCode Academy

Lesson 2 of 4 · Free to read

Exercises

Exercises — System Architecture: monolith, microservices, event-driven, serverless

Watch & learn

Course video

Open on YouTube
System Design Basics: Horizontal vs Vertical Scaling — Architecture trade-offs before you pick a stack.

Course video

Open on YouTube
RESTful APIs in 100 Seconds (+ build) — API shape you’ll generate and verify with AI.

Keep a prompt log while you work. Speed without a trail is not a skill — it is luck.

Exercise 1 — Score the matrix

Goal: pick one product and score the decision matrix. Time: 20 minutes Level: foundational

Steps

  1. Open the matrix in slides-outline.md.
  2. Score each row 1–3 per pattern for your product.
  3. Total. Decide. Write a 3-line justification.

Success criteria

  • A scored matrix + justification in learner-artifacts/<name>/matrix.md.

AI prompt hints

  • "Critique my scores. Where am I likely biased toward microservices?"

Solution sketch

Strong learners pick monolith for small-team products. Watch for trend bias.

Stretch

  • Score for a different product (different team size). Note how the result shifts.

Exercise 2 — Write an ADR

Goal: write a 1-page Architecture Decision Record for the choice from Exercise 1. Time: 30 minutes Level: intermediate

Steps

  1. Open learner-artifacts/<name>/adr-001-architecture.md.
  2. Sections: Context, Options considered, Decision, Consequences (positive + negative), Reversibility.
  3. Cite the matrix score; cite an alternative you rejected and why.

Success criteria

  • All 5 sections present.
  • At least one "negative consequence" listed.

AI prompt hints

  • "Critique my ADR as a senior architect. What's missing?"

Solution sketch

The "negative consequence" is the test of intellectual honesty.

Stretch

  • Show the ADR to a partner; collect 2 challenges; incorporate.

Exercise 3 — Spot the smell

Goal: read the architecture sketches in code-examples/typescript/architecture_sketches/; identify ≥1 smell in each and propose a fix. Time: 30 minutes Level: intermediate

Steps

  1. Read each sketch's README.md.
  2. For each, write in smells.md: smell, why it's a smell, fix.

Success criteria

  • All 3 sketches diagnosed.
  • Fixes are concrete, not just "use a different pattern".

AI prompt hints

  • "Critique my diagnosis. Is there a stronger smell I missed?"

Solution sketch

Sketches A / B / C contain distributed monolith / chatty bus / accidental microservices respectively.

Stretch

  • Sketch a 4th smell from a real project you know.

New free lessons and course updates. Unsubscribe from any email.