Like many others here I gave up after a while. The author fails to address any of the questions I had when reading:
- How many deployment artifacts do we have? How many nodes/machines running different processes?
- How do we ensure clear separation of domain boundaries (something which microservices excel at) while still staying flexible when those boundaries change (something which a monolith excels at)? Essentially: How do we prevent chaos?
- When changing one of the LEGO bricks, who is responsible for updating their usage downstream? What is the contract here?
- How many deployment artifacts do we have? How many nodes/machines running different processes?
- How do we ensure clear separation of domain boundaries (something which microservices excel at) while still staying flexible when those boundaries change (something which a monolith excels at)? Essentially: How do we prevent chaos?
- When changing one of the LEGO bricks, who is responsible for updating their usage downstream? What is the contract here?