DEV Community

Discussion on: Micro-services vs Monolith Architecture

Collapse
kdgyimah profile image
Kingsley Gyimah

This is concise. I enjoyed reading.

I also want to point out that without proper skills and knowledge, building a microservice application is extremely risky.
Just having the architecture knowledge is not enough. One would need to have DevOps and Containers experts on board since the concepts are tightly coupled with microservices. Domain modelling expertise must not be left out as well.

With that being said, the long-term benefits of having a microservices architecture to solve a complex business problem for much larger applications is well worth the investment.

Collapse
iggredible profile image
Igor Irianto Author • Edited

Thanks! I agree. At work we used both a monolith and multiple micro-services (started out with a single Rails app, now we have multiple NodeJS app microservices). To be honest, when I started I didn't really appreciate the micro-services but now that I've been here for a while, I'm much more appreciative to what the architects had done.

And yes, there is a much larger picture that is not mentioned here (pipelines, containers, testing, etc etc).

Very good points, I'm glad you brought them up!