8 What’s Inside Our Microservices?
This chapter covers
- Deciding what goes inside a microservice
- Why Business Departments matter for microservice design
- Why different departments see different things when they look at the same business object
- Master Data in a company or system
- The point to point data integration problem
- Canonical model – a solution to the problem
- Why Canonical model is actually an anti-pattern in microservice design
You won’t believe what happened. Since we implemented our microservice architecture, Fantlers Sales have been flying off the shelves. Our growth is straight up, and Bullwinkle became an overnight Internet sensation. And that is not the most amazing part.
You know WartMart, the international department store focused on selling fake warts and beauty marks? Well WartMart made an offer to buy Fantlers and Bullwinkle accepted. Bullwinkle is now a gazillionaire!
It gets even better. WartMart wants Bullwinkle to run their entire Fake Antlers division, and Bullwinkle wants us to be the CTO. Imagine us – the CTO of the Fantlers division of WartMart! We are living the dream…
8.1 How Did We Divide up the Fantlers Microservices?
Now we are part of a big global faux beauty company, we have to make sure our microservice designs can pass the test. They aren’t green field microservices that we can start from scratch. They now have to take into account all the existing applications, and even mainframe computers that have been around since the Earth first began.