CSE Roadmap

Core tier · about 4 hours · 8 parts

Part 8 of 8 · 3 min read

Exercises

Easy

Easy 1: Benefit and bill (20 minutes)

Take the six benefits in section 2. For each, write one cost in your own words and one sign that the cost is not being paid.

Done when: a table with six rows and two columns of your own text.

Hint

Start with the table in section 2 and ask what each benefit needs from the team.

Easy 2: Spot the entity trap (20 minutes)

A shop has services named Customer, Address, Order, OrderLine and Price. Explain what is wrong with this split and propose three services that follow business jobs.

Done when: a short critique and a list of three services with one sentence each.

Hint

Ask who would change when a price rule changes.

Easy 3: Choreography or orchestration (20 minutes)

For each case, say which fits better and why: (a) send a welcome email after sign-up; (b) a booking flow with five steps and an undo for each.

Done when: two answers of two sentences each.

Hint

Undo steps point to a coordinator.

Medium

Medium 1: Saga on paper (30 minutes)

Design a saga for an order with payment, stock and shipment. List each step, its undo, and what happens if the undo itself fails.

Done when: a table of steps and undos, plus a rule for a failed undo.

Hint

An undo can fail, so it must be safe to run twice.

Medium 2: Count the calls (30 minutes)

One page needs data from 8 services. Each call takes a made-up 20 ms. Compare doing them in a row with doing them in parallel, and with a mediator service. Then list two ways to cut the number of calls.

Done when: timings for three cases and two reduction ideas.

Hint

A row is the sum of the calls. Parallel is the slowest call.

Medium 3: Share the right things (30 minutes)

List ten things that 30 services might share. Sort them into "share" (for example logging) and "duplicate" (for example an address class). Give one reason for each.

Done when: a sorted list of ten with reasons.

Hint

Business names are duplicated. Operations are shared.

Hard

Hard 1: Team to service map (45 minutes)

A company has 4 teams of 6 people and a product with 8 business areas. Propose a split into services, an owner for each, and a rule for work that crosses teams.

Done when: a map of areas to teams and services, and a cross-team rule.

Hint

Count services per team before you count areas.

Hard 2: Argue against (45 minutes)

A start-up with 6 developers and one product wants microservices on day one. Write the case against, in the form of questions it must answer yes to first.

Done when: at least six questions, each linked to a cost from section 3.

Hint

Think of boundaries, automation, data and people.

Hard 3: Rewrite or repair (50 minutes)

A service has 3,000 lines and bad code. Using the replaceability benefit, decide between a rewrite and a repair. State what must be true about its interface and data for a rewrite to be safe.

Done when: a decision with conditions and a rollback plan.

Hint

A safe rewrite needs a stable interface and data that can be moved or shared during the change.