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)
• Domain-Driven Design in Practice with Michael Plöd (Online Workshop on 20th - 22nd September 2022)
• Functional Domain Models in Practice with Marco Heimeshoff (Online Workshop on 17th - 21st October 2022)
• Java Forum (Online Conference on 31st August 2022)
• E106 - CLASSIC - Steve Nouri - On Growth and Branding for AI Professionals (Online Meetup on 26th June 2022)
• Building a Culture to Take Control of Your Software (Online Meetup on 28th June 2022)
• Gravitee APIM Behind Istio Service Mesh (SkillsCast recorded in May 2022)
• Enabling Microservice Success (SkillsCast recorded in May 2022)