3 ms·
It's just about need. Most people don't need microservices. Let me repeat that. Most people don't need microservices. It's only relevant at scale. The scale I'm
by asim 4y ago
It's just about need. Most people don't need microservices. Let me repeat that. Most people don't need microservices. It's only relevant at scale. The scale I'm talking about is organizational scale and then potentially technical scale but it's mostly about solving people problems by enabling independent development of products and features.
Developers are their own worst enemy. They love shiny buzzwords and using unnecessary tools and concepts just to say they did. Conceptually you can't blame architecture patterns, that makes no sense. Blame those who choose to adopt patterns for the wrong reasons.
- tonymet 4y agoWhat 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 4y agoSLAs per product.
- tonymet 4y agometrics per product – no micro needed
- asim 4y 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 4y agoi use one today with more than 20k engineers