Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Macroservices, or several megaliths instead of one monolith, if you will.


What about going the other way and Unix-piping together hundreds of thousands of nano-services?


I 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: