What Running Kafka on VMs Taught Us About Systems Thinking

9 pointsposted 5 hours ago
by yeame
(engineering.moniepoint.com)

8 Comments

sgarland

3 hours ago

> Our Kafka setup started the way most things do in a fast-moving engineering team: pragmatically.

> Every change required SSH and port-forwarding. Our Kafka instances had no URL. You accessed them via localhost.

That isn’t pragmatism, it’s lift-and-shifting your test environment into prod. You can in fact run stuff on VMs in a repeatable and sane way; it’s called Ansible + Packer (or any other similar combo you’d prefer).

zulux

2 hours ago

I've had to learn to change how I write so I'm not accused of being a bot. No dashes, no trite pairings. (Yes that was intentional)

It just dawned on me that I've had to do this before: When PC stuff became vogue: Black vs white. Cis Female vs women.

MrBuddyCasino

3 hours ago

> „It Wasn't a Crisis. It Was a Decision.“

closes tab

hi_hi

3 hours ago

I feel seen. I find this happening about 70% of the time now. Maybe 50% of that 70% it takes a few paragraphs where my brain is squinting at something not feeling quite right before I hit the slop line, then I feel stupid for not picking it up sooner.

Give me back the days of rage bait about people’s tech preferences. At least there were opinions and beliefs being laid bare for all to see in their naked, yet occasionally dumb, beauty.

Now we don’t even get opinions or dumbness to read. It’s like humanities personalities have been Gaussian blurred to a point where I can kinda understand what’s being said, but without the richness and detail.

geodel

3 hours ago

Damn, I was at exactly same place when I closed tab and came back here. I just started reading, finding author pompous writing themselves in 3rd person.

I'd say it is crisis (of slop) and it is decision to keep generating slop nonetheless.