5 ms·
>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 a
by 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.