The three golden rules of Microservices include:
As you plan to decouple your application into smaller, independent services in general Microservice expect to split your existing teams into smaller, independent units.
Jeff Bezos, founder and CEO of Amazon.com, famously coined the idea of a “Two-Pizza team” which means teams should not be larger than what two pizzas can feed.
Componentization of single application into multiple serviceable components is the most important activity in Microservice architecture.
Best would be to start by defining a RESTful API to access this service, then plan and create an implementation using comfortable development language and platform.
Communication among bigger teams becomes complex, which results in numerous mistakes and curbing the speed of development.
Collaboration among teams focuses around API contracts and Technology standardization.
The final delivery of an application requires more than the development of the constituent components.
These components must be connected, presentation layer and additional services must be layered in, then the completed application must be delivered to users. Given that microservices must communicate using APIs.
People are more important than process. It’s key to share the lessons learned with development team, so that when you expand the scope of your microservices initiative, they are supportive and willing to embrace the change.