3 ms·
> if the stack is already pretty diverse, needs a lot of separate teams, hiring is hard, coordinating deployments is hard, etc, then it makes sense. So what yo
by gls2ro 3y ago
> if the stack is already pretty diverse, needs a lot of separate teams, hiring is hard, coordinating deployments is hard, etc, then it makes sense.
So what you are saying is that microservices are not a solution to a technical problem but a solution to organizational problems?
- pas 3y agoI'm saying that microservices as a tech-cultural phenomena (or even era) was a response to a very specific set of constraints. The whole cloud thing was new, hiring was hard, expertise was scarce, business was booming so loud people got deaf from simply thinking about it, the church of true scalability was omnipotent, tools were crude, marvelously maintained monorepos were only artifacts of seriously wet [FAAN]G-fueled dreams, etc. It made sense for Netflix, because they had a big Cassandra cluster, too much money, and a very picky organizational/hiring culture, and so on. https://www.infoq.com/presentations/microservices-netflix-industry/ https://www.infoq.com/presentations/microservices-netflix-in... (https://www.youtube.com/watch?v=TOM6UhCetQ0 https://www.youtube.com/watch?v=TOM6UhCetQ0)