“Microservices” is basically an architectural style to develop a single application having small services which can communicate using Lightweight mechanism such as HTTP resource API. This would be most suitable when you have multiple interfaces which you would like to consume in the end-user scenario. Probably this post would be a summary of the Keynote from Martin Fowler.
Also microservices are nothing but a meaningful subset of SOA. so it can never by considered as an alternative or to replace SOA.
- Monolithic puts all functionality under one application process where in Microservice puts features/services into a separate servics.
- During the deployment to a distributed environment monolithic service has similar replica of its services where in Microservices can be deployed based on the need basis.
Common characteristics outlined in his talk are:
- Componentization via services
- Organized around business capabilities
- Products not projects
- Smart end points and dumb pipes
- Decentralized Governance
- Decentralized Data management
- Infrastructure Automation
- Design for failure
- Evolutionary design
Few important takeaways according to me:
- Componentization via Services: The componentization during development should be in such a way that it is independently replaceable and upgradable. Microservices uses the library and services can be built as components.
- Organized around business capabilities: Whenever the applications are built generally the teams are divided as UI, Middleware and DBAs. Instead the team should be organized around the communication channel in the business according to Conway’s law. These microservices dev teams are cross functional teams which has an broad spectrum resources with UX, Persistent Storage and project management knowledge. This helps align quicker to understand the business context in faster ways
We will discuss more on the other takeaways in the upcoming post.