Member-only story
Common Mistakes in Microservices Architecture
If you read my previous articles, we have discussed what needed to design a robust, reliable and easy to maintain Microservices architecture. In reality, things are not going in correct way always. Microservices requires thorough design and a lot of the work is happening before writing the first line of code. They are not “Fire and Forget”. You can not just say to the developers that we are going to do Microservices and good luck with that ;).
In-fact, its quite easy to make mistakes that will cause the project to fail. If you are thinking seriously about Microservices, make sure to not do these mistakes.
No Well-Defined Services
The first common mistake is the no well-defined services. To understand about that, lets go back to the architectural process I wrote earlier.
I wrote about three steps,
- Component mapping
- Selecting the technology stack
- Designing the architecture
