NOTE: This is currently highly work in progress. Be sure to check out every now and then for more detailed information and explanations about the individual modules.
This repository contains some sample code for my talk "Refactoring to a System of Systems" that outlines what problems developers can run into if they split up a system into multiple ones but transfer interaction patterns of typical monolithic applications as is. Slides of that talk and a recording of it will be linked here as soon as they become available.
The repository contains five different projects, each of them potentially split into multiple ones in turn. For details on the individual ones, please refer to the READMEs conatined in the individual project's root.
The sample application is built around an e-commerce domain with the following Bounded Contexts:
- Catalog - containing product master data (in our case product name and price).
- Inventory - keeping track of the number of available items per product.
- Order - keeping track of orders placed by customers.
The individual modules provide sketch implementations of these Bounded Context and the following interactions between them implemented:
- When a product is added, the inventory needs to register empty stock for that product.
- When an order is completed, the inventory needs to update the stock for the products ordered.
- The Monolith - a typical monolithic Spring Boot application with the Bounded Contexts implemented in packages and the interaction being based on active invocations of Spring beans residing in a different BC.
- The Microlith - the former approach transferred into separate systems but keeping the same interaction patter of synchronous, non-idempotent operations. The systems invoking each other via HTTP calls.
- The Modulith - an improved version of the monolith with the Bounded Contexts interacting via Spring application events and event listeners.
- SOS Messaging - the individual Bounded Contexts implemented as separate systems and the interaction implemented via a Kafka message broker.
- SOS REST - the individual Bounded Contexts implemented as separate systems and the interaction implemented via the events exposed as REST resources.
The repository should build by simply running mvn clean install using a recent JDK 8.
Sample code uses Lombok, which means that you need a Lombok-enabled IDE in case you want to import the projects into it.
For detailed instructions about how to work with the individual projects, see the individual module's READMEs.