5 ms·
Macroservices, or several megaliths instead of one monolith, if you will.
by moffkalast 1y ago
Macroservices, or several megaliths instead of one monolith, if you will.
- Rendello 1y agoWhat about going the other way and Unix-piping together hundreds of thousands of nano-services?
- sally_glance 1y agoI think it's called serverless or FaaS today? But why choose, just do all three at the same time! Actually you don't even have to choose, it will naturally happen when transitions are never fully completed... So before you know it you're stuck with a partially integrated legacy monolith which talks to a legion of half-baked microservices and emits events processed by arcane workflow engines orchestrating lambda execution.