CSE Roadmap

Common tier · about 4 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes eighth

In this module you will

  • Find seams in an existing codebase and rank them by which to split first.
  • Explain the strangler pattern and when it is the right tool.
  • Split a shared database step by step: foreign keys, static data, shared tables and shared records.
  • Describe what happens to transactions when one database becomes two, and the three ways to cope.
  • Keep reports working after the data has been split.

Most real systems start as one deployment. Pages 5 to 7 described the target. This page describes the journey, which is where most of the work and most of the risk lie. A split done in one big step usually goes wrong. The book used is "Building Microservices" (BM), chapter 5, with the strangler pattern from chapter 4. The numbers are made up to show the idea, unless the text names a book.