Top Highlights

• Often, organizations that adopt microservices also have adopted continuous delivery. Bottom line: implementing microservices is a paradigm shift for management as well as developers and architects.
• Any coupling between services is restricted to the service layer, with no coupling at a code or database level.
• Microservices have a single functional purpose. That is, they have a single business purpose. They do one thing and do it well. To level set, the term ‘functional’ is borrowed from the term ‘functional requirement.’
• Functional requirements are typically business requirements; they support doing business directly in some way. In essence, the terms ‘functional’ and ‘business’ can be used interchangeably.
• As a byproduct of having a single functional purpose, most business changes affect a small number of services (preferably only one service).