3 ms·
What would be the difference between microservice and a monolith with separate folders, separated by team? If teamA calls teamB's code, they have to import. If
by tonymet 5y ago
What would be the difference between microservice and a monolith with separate folders, separated by team? If teamA calls teamB's code, they have to import. If teamA needs a change to teamBs code, they submit a PR?
Microservices are not needed for scaling an org .
- wting 5y agoSLAs per product.
- tonymet 5y agometrics per product – no micro needed
- asim 5y agoHave you ever shipped a monolith across 10 product teams? Everyone is working on different features, different branches, etc. The monolith becomes the bottleneck and you end up architecting processes to cater to its weaknesses where it should actually work to your strengths. Microservices inherently build that in, not just into the development model but the entire workflow from source to running and beyond. People are often disillusioned by the idea of the breakdown of the source code but fail to understand that the technical platform and processes in the pipeline enable independent product teams to move faster.
- tonymet 5y agoi use one today with more than 20k engineers