CSE Roadmap

Common tier · about 3 hours · 7 parts

Part 7 of 7 · 3 min read

Exercises

Easy

Easy 1: Sort the statements (20 minutes)

Label each as a decision, principle, characteristic or technology choice: "99.95 percent uptime"; "services may not share databases"; "prefer events over calls"; "use MySQL 8".

Done when: four labels with a reason each.

Hint

A rule you can check is a decision. A "prefer" is a principle.

Easy 2: Find the cost (20 minutes)

For each option name one benefit and one cost: a single shared database for all services; a cache in front of the database; asynchronous messaging for sending emails.

Done when: three pairs of benefit and cost.

Hint

Think about extensibility, security, speed and complexity.

Easy 3: Read an ADR (20 minutes)

ADR 42 says "Superseded by 68". ADR 68 says "Accepted, supersedes 42". Which is in force? What should a new team member read first and why?

Done when: a one-paragraph answer.

Hint

The newer one is in force. The old one explains the earlier reasoning.

Medium

Medium 1: Topic or queues (30 minutes)

A news site sends each new article to search indexing, a push notification service and analytics. Use the auction analysis and decide topic or queues. State the factors that tip the decision.

Done when: a decision, a table of three factors and one condition that would reverse it.

Hint

Ask who may see the data and whether consumers scale differently.

Medium 2: Write an ADR (30 minutes)

Write an ADR for "use a managed database instead of running our own". Fill all seven sections. Include one number in Consequences and a compliance check.

Done when: a complete ADR under one page.

Hint

Put the number in Consequences, such as hours saved per month (made up).

Medium 3: Decay watch (30 minutes)

Choose a characteristic (build time, page load time or deploy frequency). Define a measurable limit, a fitness function that checks it and what happens when it fails.

Done when: a limit, a check description, a trigger and an owner.

Hint

Choose something a script can measure.

Hard

Hard 1: Rescue the reason (45 minutes)

A system uses direct HTTP calls between services, and a new architect wants to move all of them to messaging. List the questions to ask before changing, the characteristics at risk, and the evidence you would collect. Write the ADR that records the final answer.

Done when: a question list, a risk table and an ADR.

Hint

The original reason may have been latency.

Hard 2: Challenge a decision (45 minutes)

An architect decides that all databases are private to one service. Teams object. Write the three strongest objections, the reply to each, and a variance process for the one case where sharing is truly needed.

Done when: three objections with replies and a variance outline.

Hint

Typical objections are speed, duplicated data and extra calls.

Hard 3: Plan a vitality review (50 minutes)

An architecture is four years old. Design a review: what to measure, what to ask the teams, what to compare with the original characteristics, and how to present a "keep, change, retire" result.

Done when: a review plan with five measures and a decision format.

Hint

Compare today's measured numbers with the original targets.