I find containerization useful regardless and Kube allows a simple orchestration solution so I can use a single machine for many things without too much trouble. No need to worry too much about ports and log rotation and all that. Just a nice batteries-included solution. The primitives are also trivial to reason about.
And writing YAMLs sucked in the old days but now with kustomize built in you can easily do everything you want with templating. LLMs can write it all.
As an aside, please prompt your agent to be more concise. Totally unnecessary text expansion. “I didn’t do this to be clever”. Pure filler text. No one talks like this.
On containers, I do use them, just not an orchestrator, and your single machine point is the strongest counter to the piece. I underweighted it. What put me off was the operational surface I would have to learn and keep running on my own, not the YAML. But ports, log rotation and supervision handled for you is a real benefit that I am currently doing by hand, so I will look at it properly.
And yes, I draft with an assistant and edit, and it padded this one, that's on me. smiles.
> Microservices solve a real problem too, and it is mostly organisational rather than technical. When you have enough engineers that they are stepping on each other in one codebase, and enough teams that release schedules collide, splitting the system along team boundaries buys independence.
grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too
I find containerization useful regardless and Kube allows a simple orchestration solution so I can use a single machine for many things without too much trouble. No need to worry too much about ports and log rotation and all that. Just a nice batteries-included solution. The primitives are also trivial to reason about.
And writing YAMLs sucked in the old days but now with kustomize built in you can easily do everything you want with templating. LLMs can write it all.
As an aside, please prompt your agent to be more concise. Totally unnecessary text expansion. “I didn’t do this to be clever”. Pure filler text. No one talks like this.
Fair on the length, I will tighten up.
On containers, I do use them, just not an orchestrator, and your single machine point is the strongest counter to the piece. I underweighted it. What put me off was the operational surface I would have to learn and keep running on my own, not the YAML. But ports, log rotation and supervision handled for you is a real benefit that I am currently doing by hand, so I will look at it properly.
And yes, I draft with an assistant and edit, and it padded this one, that's on me. smiles.
> Microservices solve a real problem too, and it is mostly organisational rather than technical. When you have enough engineers that they are stepping on each other in one codebase, and enough teams that release schedules collide, splitting the system along team boundaries buys independence.
grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too
seem very confusing to grug
[dead]