CSE Roadmap

Common tier · about 4 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes sixth

In this module you will

  • Find bounded contexts in a business and say what each one shares and what it hides.
  • Name a service by the capability it offers, and not by the data it holds.
  • Use three ways to discover components: actors and actions, event storming and workflows.
  • Check a draft design against architecture characteristics and split a part that needs different levels.
  • Spot the two classic mistakes: splitting too early and splitting along a technical layer.

Page 5 listed what microservices cost. Most of that cost is set by one decision: where the lines between services are drawn. A wrong line is expensive, because every change then crosses it. This page gives the tools for drawing lines well, and two warning stories. Two books are used. "Building Microservices" (BM), chapter 3, covers bounded contexts and the two stories. "Fundamentals of Software Architecture" (FSA), chapter 8, covers component discovery. The numbers are made up to show the idea, unless the text names a book.