On 16/01/2021 2:29 pm, mike wrote:
> We hear a lot of positives using microservices since it will
> be easier to deploy separate and independen. So I thought that
> it might be possible to transition over to use microservices since
> products tends to be virtualized in the cloud.
Our company transitioned from a huge monolith to 35+ Microservices.
Microservices bring with them their own set of problems,
so they are definitely not the "silver bullet" to fixing the problems
associated with a monolith project.
I would highly recommend you do some internet searches on reasons not
to use a Microservice - just so you get the facts from both sides
and have more information before you start making changes to your code.
The question you should ask is:
What do you think the Microservice Architecture will give you?
A monolith project doesn't need to be maintenance nightmare either. It
can be cleaned up and refactored.
A possible alternative is to embrace Java 11 and split your project up using
Java Modules to represent domains in your business model. You could have
many of the same benefits Microservices offer and also new improvements,
like much improved latency and memory usage, easier deployments, easier
security model etc.
Many of our Microservices became a nightmare to maintain too, so we
started introducing the Ports & Adapters architecture inside a Microservice
project to help improve things. This could equally have been applied
to a Monolith project too.
Regards,
Graeme