3 ms·
i think he is skipping a couple of points. For example the deployment aspect: - monolith single deployable unit. - microservice multiple independently deployab
by je42 6y ago
i think he is skipping a couple of points.
For example the deployment aspect:
- monolith single deployable unit.
- microservice multiple independently deployable units.
Multiple teams on a monolith:
- you have to coordinate releases and rolebacks...
- code base grows and dependencies between modules (that have shouldn't have dependencies on each other as well, unless you have a good code review culture.)
- deployment get slower and slower over time.
- db migrations also need to coordinates over multiple teams.
These problems go away when you go microservices.
Of course you get other problems.
My point is, in the discussion microservices vs monolith you need to consider a whole bunch of dimensions to figure our what is the best fit for your org.
- giulianob 6y agoStill don't need microservices. What you're referring to is just SOA which has been around for a couple of decades. Microservices typically outnumber engineers or aren't too far off.
- dragonwriter 6y ago> What you're referring to is just SOA which has been around for a couple of decades “Microservices” is just a new name for SOA that ditches the psychological association SOA had developed with the WS-* series of XML-based standards and associated enterprise bloat.