Re:I've been merging microservices back into the monolith
by jiraticketmach on Tuesday December 22, 2020 @08:08AM
(#25505856)
Microservices were/are an attempt of standardizing software development practices at really large organizations.
For example: your typical big bank has hundreds or thousands of teams (both internal and through professional services companies) developing all kinds of applications under different technologies/hardware.
In this case due to domain/organizational scale it is not feasible to have a mono repo (or 2, or 3) with a giant codebase.
And as a result the typical situation is an expensive hell full of code duplication, ad-hoc integration methods, nightmarish deployments and such.
Microservices are helpful in situations like this (even if they are not perfect).
But for a company with a couple of development teams and a domain that can be understood almost entirely by a couple of business analysts, it´s overkill.
For example: your typical big bank has hundreds or thousands of teams (both internal and through professional services companies) developing all kinds of applications under different technologies/hardware.
In this case due to domain/organizational scale it is not feasible to have a mono repo (or 2, or 3) with a giant codebase.
And as a result the typical situation is an expensive hell full of code duplication, ad-hoc integration methods, nightmarish deployments and such.
Microservices are helpful in situations like this (even if they are not perfect).
But for a company with a couple of development teams and a domain that can be understood almost entirely by a couple of business analysts, it´s overkill.