cloudpatterns.appClassroomKatasWhiteboardBlog
Station: MonolithStep 1 of 12Start

Monolith: one deployable

Lesson~14 minStep 1 of 12
  1. Start (current)
  2. Predict
  3. Predict 2
  4. Name the parts
  5. Explain
  6. Explain 2
  7. Explain 3
  8. Explain 4
  9. Explain 5
  10. Apply
  11. Check
  12. Wrap up

Checkout, the online shop, didn't start as a set of services. If you've met it in the Resilience line, this is its earlier shape: one app. The cart, orders, payments and stock checks are all in one codebase, built together and shipped together, on their own app servers in front of one database.

It has worked well for two years. Now three teams work on it. On Monday the cart team fixes a typo on the cart page — a one-line change. It doesn't reach shoppers until Thursday.

In the planning meeting someone says: "This is what you get with a monolith. Let's split Checkout into services."

This one is reading and questions — no simulation.