2 Starting with Microservices
This chapter covers
- Key design principles for a well designed microservice
- Why Bullwinkle wants to sell Fake Antlers
- How to start designing microservices, with a name, data, and responsibilities
- How to use a Microservice Design Language (MDL) card to represent a microservice
- How to analyze a collection of user stories, create a customer journey and identify the flow and the responsibilities
- How to use MDL cards to map out the sequence and communication
NOTE
MDL cards are described in this chapter and will be used to represent microservice designs in the rest of this book.
Why do we build microservices?
- To be cool?
- To look knowledgeable?
- To have the latest buzzword on our resume?
Well, yes, yes, and definitely.
But as we learned in the last chapter, Microservices make promises:
- Be much easier to code
- Be much easier maintain
- Speed up development from idea to market
- Increase innovation and business agility (this is usually the number #1 selling point for the business)
- Make it easier and faster to fix bugs
- Make it easy to use different technology stacks and tools – the right tool for the problem
- Make scaling simple and automatic
- Turn microservice designers into Rock Stars