3 ms·
>Availability Risks. A single regression within a monolithic code base can bring the whole system (in this case, all of Uber) down. A single regression in your
by charcircuit 3y ago
>Availability Risks. A single regression within a monolithic code base can bring the whole system (in this case, all of Uber) down.
A single regression in your isEven microservice can also take the whole system down. You can mitigate this by slowly rolling out new versions to try and catch regressions early so you can revert.
>Risky, expensive deployments. These were painful and time consuming to perform with the frequent need for rollbacks.
Code that is going to be deployed all needs to be deployed. Painful deploys are going to happen with microservices too.
>Poor separation of concerns. It was difficult to maintain good separations of concerns with a huge code base. In an exponential growth environment, expediency sometimes led to poor boundaries between logic and components.
Making libraries will boundaries without having to do an expensive network call.
>Inefficient execution. These issues combined made it difficult for teams to execute autonomously or independently.
Monoliths let you work independently too. You go in and change something and now it is changed. No part of monoliths make it harder as a single person or team to make changes.
Also keep in mind Uber ships Android and iPhone apps which are monoliths. They don't force you to install an app for entering a location, an app for making a payment, an app for looking up pricing, etc.
- tsss 3y ago> isEven microservice If you have one then you're doing it wrong and don't get the most basic thing about microservice architecture. Microservices must be business-aligned and as independent as possible. > They don't force you to install an app for entering a location, an app for making a payment, an app for looking up pricing They probably do. I bet their Android app has independent dynamic feature modules that are loaded on demand.
- charcircuit 3y ago>If you have one then you're doing it wrong No. Microservices as the name suggests are micro and their functionality can be pretty limited. If you don't have any trivial microservices then you are doing it wrong. You may be objecting because of how inefficient it seems to put a function like that over a network call, but that just makes the performance downside of the microservice architecture clearer.
- dzikimarian 3y agoCan you cite a source that says "micro" means "single procedure per service"? Or did you pull it from thin air and you are going to argue that everybody else is wrong?
- charcircuit 3y agoI never claimed single procedure per service so I will not go and find a citation for it. Yes, I will argue that if you are building full services then you are not doing microservices. You are just doing services. With microservices you will see CRUD services that manage a single resources or services that doing validation which sometimes can very simple like for example isEven.
- tsss 3y agoWhatever it is you are doing, it is horrible.