So you broke it into tiny pieces. How should you put it back together?

Breaking down the monolith into microservices is a good thing. It lets you decouple the rates of change of our system, assign individual accountability, apply selective and appropriate scaling. But business isn't about atoms. Its about molecules. The value of combining two or more services together on-demand often delivers key business value that is greater than the sum of the parts. If you start writing lots of glue code to put these composites together we start to rebuild the monolith - surely that's not what was supposed to happen...

Grab your tickets now to µCon: The Microservices Conference 2017!

YOU MAY ALSO LIKE:

• Resource Oriented Microservices (SkillsCast recorded in November 2016)
• Understanding Distributed Systems using OpenTelemetry with Liz Fong-Jones (Online Course on 22nd September 2021)
• Design Patterns in Action — Full‑Day Workshop [SAG Digital 2021] (Online Course on 11th October 2021)
• Software Architecture Gathering Digital 2021 (Online Conference on 13th - 14th October 2021)
• Patterns for a Successful Cloud Native Transformation (SkillsCast recorded in June 2021)
• Managing Commercial Platforms: The Architect’s Emerging Skill (SkillsCast recorded in June 2021)