This is such a rose-tinted glasses view of Microservices, which introduce a great amount of complexity, cost, new potential areas for failure, and ultimately shifts the problem around rather than solve it. In reality you wouldn't have a single server for a monolith, you would have a load balanced set of smaller cheaper servers, arranged in availability sets. The database is usually the area to focus on for scalability and availability, and you would probably look at sharding. With Microservices you introduce new issues such as eventual consistency, lack of transactional integrity, sagas, messaging (topics, competing consumers, compensating messages, message versioning, dead lettering, ordered delivery), network partitioning etc. Then you need container orchestration, Not to mention that one of the touted advantages of Microservices - that you can use different technologies for different components, invariably ends up being a mess with almost zero benefit, and dev teams going off on a tangent. Most companies simply do not need the proposed benefits of Microservices for the effort required to achieve them, Hence so many people moving to modular monoliths, rather than starting from a Microservices approach.
Microservices a worked great for my previous team, but indeed we had an entire team dedicated to handle all the required infra. With all that infra in place I was able to do microservice development pretty well, no complaints.
![[UNCUT] The Loyal Pin ปิ่นภักดิ์ EP.6 (2/4)](http://i.ytimg.com/vi/GgeGQOP10RQ/mqdefault.jpg)
This is such a rose-tinted glasses view of Microservices, which introduce a great amount of complexity, cost, new potential areas for failure, and ultimately shifts the problem around rather than solve it. In reality you wouldn't have a single server for a monolith, you would have a load balanced set of smaller cheaper servers, arranged in availability sets. The database is usually the area to focus on for scalability and availability, and you would probably look at sharding.
With Microservices you introduce new issues such as eventual consistency, lack of transactional integrity, sagas, messaging (topics, competing consumers, compensating messages, message versioning, dead lettering, ordered delivery), network partitioning etc. Then you need container orchestration,
Not to mention that one of the touted advantages of Microservices - that you can use different technologies for different components, invariably ends up being a mess with almost zero benefit, and dev teams going off on a tangent.
Most companies simply do not need the proposed benefits of Microservices for the effort required to achieve them, Hence so many people moving to modular monoliths, rather than starting from a Microservices approach.
Microservices a worked great for my previous team, but indeed we had an entire team dedicated to handle all the required infra.
With all that infra in place I was able to do microservice development pretty well, no complaints.
Don't usually comment but with examples and animations made it much easy going to watch all your videos keep up good work
Glad you like them!
Can C# be used for micro saas or do we have to use a microsaas specific language like Go for that?
Microservices are language agnostic.
Well explained. Thanks man.
You bet!
Excelente trabajo, Julio! Muy buen video!
Que bueno que te gusto!