CSE Roadmap

Common tier · about 4 hours · 7 parts

Part 1 of 7 · 1 min read

Why this page comes fourth

In this module you will

  • Describe the pipeline style: pipes, the four kinds of filter, and where it fits.
  • Describe the service-based style: 4 to 12 coarse services, one shared database, and how to partition that database.
  • Explain the event-driven style with its two topologies, broker and mediator, and the trade-off between them.
  • Show how request and reply works in an event-driven system, and why it is built on a correlation id.
  • Compare the three styles on partitioning, deployment, strengths and weak points.

Page 3 covered the single deployment. This page covers three further styles that sit between a monolith and full microservices. The pipeline is a monolith shaped like a conveyor belt. Service-based is the first step into several deployments. Event-driven changes how the parts talk. Level 6 explained the messaging tools behind the last one, and this page shows the architecture built from them. The book used is "Fundamentals of Software Architecture" (FSA), chapters 11, 13 and 14. The numbers are made up to show the idea, unless the text names a book.