{"id":2736,"date":"2021-09-16T04:34:34","date_gmt":"2021-09-16T04:34:34","guid":{"rendered":"https:\/\/www.cloudnowtech.com\/blog\/?p=2736"},"modified":"2021-12-09T17:29:57","modified_gmt":"2021-12-09T11:59:57","slug":"is-my-microservice-actually-a-distributed-monolith-in-disguise","status":"publish","type":"post","link":"https:\/\/www.cloudnowtech.com\/blog\/is-my-microservice-actually-a-distributed-monolith-in-disguise\/","title":{"rendered":"Is my Microservice actually a Distributed Monolith in disguise?"},"content":{"rendered":"

Has your app modernization exercise gone wrong?\u00a0<\/span><\/p>\n

Application redevelopment into microservices-based architecture can result in apps that incorporate the complexity of microservices with the shortcomings of a monolith – the worst of both worlds! This is called a Distributed Monolith.<\/span><\/p>\n

Proper microservices-based architecture creates distinct units with clearly defined inter-service boundaries. The application is fragmented into individual business services, each of which functions independently of the other, communicating through APIs. Each can even be hosted on a different server.\u00a0<\/span><\/p>\n

On the downside, they are much more complex and require more tech support. However, since they use fewer resources and are more scalable, and enable an organization to more easily evolve its technology stack, microservices-based architecture is the future of application development and application modernization<\/a>.<\/span><\/p>\n

A distributed monolith, on the other hand, combines the worst part of microservices-based architecture – the complex containerized structure – with the lack of scalability, slow processing and complex editing of a monolithic application.<\/span><\/p>\n

Deployed like a microservice, the application is structured like a monolith in a single package of source code, configurations, libraries, and every other dependency in a single container.\u00a0<\/span><\/p>\n

As a result, artifacts are large, slow and are very resource-intensive. Even worse, failures cascade from one container to the next, and any change on any service can require a complete rebuild and redeploy.\u00a0<\/span><\/p>\n

The whole point of microservices-based architecture is that a DevOps<\/a> team should be able to add \u201cjust one thing\u201d, without redeploying the entire codebase.<\/span><\/p>\n

Distributed monoliths are also not designed for distributed systems, so horizontal scaling is inefficient.<\/span><\/p>\n

What are the signs that you\u2019ve ended up with a distributed monolith?<\/span><\/h3>\n