You must log in or # to comment.
It’s really not, you’ll be thankful you have it once the system grows too big.
5 mins build and test times Vs 1hr build times.
I know that can be achieved by setting a monolith up to be more segregated in design, but my experience so far is that that rarely happens.
Ms architecture forces the segregation, which helps keep me sane (:
Exactly! Monoliths can work in theory but, in practice, end up becoming bloated messes since it’s just easier to do so.
There is no one-size-fits-all architecture. Microservices are fine, but probably not for you.
IMO there are two underrated benefits:
- It enforces separation of concerns
- It provides options to OPS.
Designing for micro services doesn’t mean you need to deploy it as micro services. You can deploy it as a monolith and configure it too skip the network stack
I wouldn’t mind seeing a new Micro Kernel. The Ethernet stack could be rebooted and drivers without taking down the whole computer module by module.
There are advantages to each.
People shitting on microservice architecture never worked in a truly large company (1000+ devs)
Negativity comes from the experience of splitting a small project into microservices, which I do agree is bullshit .
