Learning best practices for microservices

When starting a new application, the first and foremost question we should be asking ourselves is whether the microservices architecture is a good fit. This starts with an analysis of the application requirements and the ability to divide the requirements into separate and individual components. If you see that your components frequently depend on one another, this is an indicator that the segregation of components may require reworking, or that this application may not be a fit for the microservices architecture.

It is important to make this decision of whether to use microservices right in the early phase of an application. There is a school of thought that says that it is better to start building an application using monolithic architecture to avoid the additional costs of microservices in the beginning. However, this is not an advisable approach. Once we have built a monolithic application, it is difficult to transform it into microservices...