DEV Community

Discussion on: When should you choose Microservices instead of a monolithic CMS?

Collapse
 
laxmariappan profile image
Lax Mariappan

thanks for such a detailed reply.

I am currently stuck on a CMS project with the module vs version compatibility problem. It seems we have to upgrade to the latest version of the CMS but many modules are not yet available or expensive.

The client doesn't want to upgrade as it is like building the entire application from scratch. The same story with 3 other projects too.

So Microservices could be a better way than monolithic CMS in my experience.

Questions:

Can we use microservices even for a small website or web app like a corporate website, blog, etc?

Do microservices have any performance-related issues?

Collapse
 
dorelljames profile image
Dorell James

Yes, you can. Microservices is just an approach really of building things. I think it's important to note that going this approach requires that you have at least a good understanding of how monolithics work - that way you can effectively see where you could decouple and create modules that are as much as possible independent from each other. Most websites that only require a small portion of special functionality like processing payments, for example, can go with serverless (FaaS) to add custom logic which is normally done via backend app.

Lastly, to be honest, performance related issues are part of how well an is developed. I think for the most part with microservices since they're really focused on one business logic, I don't think it'll suffer from the said issue any time soon.