Monolith vs Microservices is always an interesting topic. The only right answer is "Whatever suits you the best". You don't have to strictly stick with either one. You can build a monolith for your core product development and then as you add features to it you can build smaller services to cater them. The major drawback I have experienced is in the SRE & Monitoring part. If a transaction fails, you have to do a lot to do the RCA. Which microservice exactly failed? Did it fail because of a dependent microservice? Is it down? these are things the developer has to ponder upon. Secondly if you have a small team then microservices can become hell. Finally, if you are getting intended results i.e. latency & scalability with monolith, go with it. A monolith is easier to maintain, in terms of Ops, than microservices.
Passionate about education, fintech, Python, Javascript, progressive growth, and full-stack development.
Sometimes I write code, sometimes I just write.
A majority of the time, the monolith does provide the intended results. Again, it would also be dependent on how fast the features need to be shipped. Well architected microservices can serve the needs of the system given enough time to test them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Monolith vs Microservices is always an interesting topic. The only right answer is "Whatever suits you the best". You don't have to strictly stick with either one. You can build a monolith for your core product development and then as you add features to it you can build smaller services to cater them. The major drawback I have experienced is in the SRE & Monitoring part. If a transaction fails, you have to do a lot to do the RCA. Which microservice exactly failed? Did it fail because of a dependent microservice? Is it down? these are things the developer has to ponder upon. Secondly if you have a small team then microservices can become hell. Finally, if you are getting intended results i.e. latency & scalability with monolith, go with it. A monolith is easier to maintain, in terms of Ops, than microservices.
A majority of the time, the monolith does provide the intended results. Again, it would also be dependent on how fast the features need to be shipped. Well architected microservices can serve the needs of the system given enough time to test them.