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

My opinion on Kubernetes is that it's great orchestration software that is trying to fix poor underlying application architecture issues. The biggest underlaying software application architecture issue today is the idea of a single responsibility worker. Why do applications have one worker only working on messages from one queue? This architecture looks great on a whiteboard, but has issues around spikes in traffic, uses tons of unused server resources, and requires lots of custom software plumbing. The solution is a generic worker that does work from any queue. It is such an obvious fix to lots of the scaling issue that large software applications face today. I'm personally only using Tempral.io, which is a generic worker orchestrator, from now on when making large distributed applications.


I think this is due to "needing teams to be independent" which for some orgs is a real thing (Conway's law) but there are small teams trying to build microservices, which, IMO, is a bad idea.


I don't think the two are mutually exclusive




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

Search: