Monolith or Microservices?
- Jitu Ranjan
- Jul 16, 2023
- 1 min read
The number of mentions of “microservices architecture” plunged 42% between January 2019 and September 2020, according to a recent Gartner social media analytics study. This trend points to growing disillusionment with microservices architecture.
Overuse of any new architectural styles has been a trend in the software industry and microservices are nothing new. The draft is a summary based on references, personal experiences and stories heard from peers i.e. most of the firms aren't ready to do this switch yet!
To keep it short, the following factors should be good enough for a firm or an individual to opt for a monolith design over microservices and should be okay to start with!
Firm DevOps practice is not mature enough
Ease of switching between modules boundary and maintaining code
Pre-defined platform technical stack e.g. programming languages, frameworks, patterns, etc.
Consistency takes over availability as one of the key NFRs
As a microservice evangelist, I would rather see the following factors to be in place before picking microservices as an architectural style
A matured DevOps culture with the capability to spin up a machine fast, deploy a service in an automated way, etc.
A matured alert and monitoring capability to manage availability
A matured firm's culture around readiness for disruptions, communications, right team layouts, services organized to deliver business, etc.
In short, it's not bad to use an old methodology/architecture as long as it does the job and makes sense to switch only after a thorough transformation analysis and validation of any new product/architecture.
Commentaires