5 ms·
You can split things up you don't have to though. Teams operating independently is fairly orthogonal to this.
by qaq 3y ago
You can split things up you don't have to though. Teams operating independently is fairly orthogonal to this.
- Sparkyte 3y agoYeah no I get you. You just want a monolith to be purposeful when you design one. Not multi-purposeful. This is also at the limitation of a programming language. I am kind of kubernetes guy, but I am dying because it relies heavily on a virtualize network distributed. It would drastically increase the performance if kubernetes clusters were built like monoliths and each kubernetes node handled traffic independently. So of like keeping it all in the same rack. Only leaving the rack if needed. But I keep seeing bad technology decisions repeated over and over. I stopped pushing because some person with a bigger title would say this is good design. Big kubernetes clusters eventually fail. Multiple small clusters survive.
- qaq 3y agoReplacing function call with network call does not really solve any org issues. There is pretty much 0 difference if teams are shipping "modules" for a monolith vs a microservice outside of much simplified CI/CD setup in case of monolith. You can gain some scaling efficiencies from scaling services independently but it's a minor advantage for most projects.
- Aeolun 3y ago> You can gain some scaling efficiencies from scaling services independently Not necessarily, because if you scale only one of your services all the other services do not benefit at all. Having microservices would only be better in that instance if they actually consume the resources they are given.