Michal Bryxí> Upgrade to a monolith
YouTube
gbsills@MichalBryxi Hmmm.... two things.
Thing 1. The only valid reason that there has every been to divide an application into microservices is to split the work across multiple development teams.
Thing 2. Developing microservices software is a lot of work, but you can definitely avoid the the problems of coupling he was describing with a lot of upfront design.
**Thing 2.5. People generally don't want to spend any time on upfront design.
@gbsills I believe he addresses both of the points in his video.
@MichalBryxi Yeah he did. I am "triggered" by this topic I think.😂 Situations like a team in Indonesia, China, and the US working on a monolith, a single team using a microservice because it wt as the "right thing to do", but using an "Agile Architecture" methodology instead of designing things up front. Troubled times.
@gbsills Oh wow. I didn’t think anything would feel more like anti pattern than microservices, but microservice (singular) is next level 😬
@gbsills I just don’t see this type of architecture as net positive for any size of project I’d like to work on.
- A laptop can expedite 100s to lower 1000s RPM from a monolith per second without breaking a sweat
- Does your API absolutely need 10k-100k RPS or is that actually imposed by the chattiness of your microservices?
- Using multiple languages/frameworks/etc. sounds like a win, but it has so many traps that I would just sum it up as: perceived gains now vs huge costs later
- A laptop can expedite 100s to lower 1000s RPM from a monolith per second without breaking a sweat
- Does your API absolutely need 10k-100k RPS or is that actually imposed by the chattiness of your microservices?
- Using multiple languages/frameworks/etc. sounds like a win, but it has so many traps that I would just sum it up as: perceived gains now vs huge costs later
@MichalBryxi The problem is that while the micro-service architecture does work for some situations, those situations are edge conditions. For example, would you even consider building the entire Amazon customer facing website as a single monolithic application? It isn't a matter performance, it is the scale of the complexity and workforce. You'd be insane to build something like that as a monolith. On the other hand, you are unlikely to be building another Amazon.
I think the problem is that people try to apply architectures to situations that they don't match. It is often a matter of programmers trying to impress other programmers with their brilliance. 😉
@gbsills Also: Yes exactly. New, shiny…