3 ms·
Tried myself to go down that road, came back to System V and cron. At most docker compose, but k8s: never again. It is way too complex for small deployments, I
by vander_elst 5y ago
Tried myself to go down that road, came back to System V and cron. At most docker compose, but k8s: never again. It is way too complex for small deployments, I need to many levels of abstraction and indirection. If I absolutely need reproducibility I can ln then configurations that I want to track in a repo and that's it.
- spmurrayzzz 5y agoEven for large deployments, I've always viewed this quandary as: what is the true opportunity cost of not using this when I have working docker solutions running at scale today? And how much time do I need to invest to get to subject matter expertise parity? The calculus there has never panned out for me, especially for any service architectures with non-trivial networking constraints. But I still do love playing around with platform to learn about it, some great ideas overall (even if complexity abound).