I have to say, it works pretty good. I tested it by creating a Kafka cluster here: https://x.com/kozlovski/status/2050943790580457646

In <15 minutes it got everything up and running - the Kafka brokers, the Kafka controllers, schema registry, Grafana. Pretty impressive

are there really no other maintenance tools that do this already? seems like a low hanging fruit?

the irony of using Claude to create this lol

it wasn't https://x.com/theo/status/2048628814755012945

Yeah, which is why this Ursa-for-Kafka (UFK) fork can be a drop-in replacement. It holds both the classic Kafka topics with disks, and the Ursa engine topics that have higher latency.

I agree with your assessment re: latency. I've been very vocal about this ever since this type of architecture came out.

It could also be that the world as a whole cares less about privacy today than they did seven years ago. Without a relative measurement from a similar platform, it's a bit of an empty statement

One thing that has certainly changed is that algorithms have become more aggressive. If your content isn't performing well, it gets hidden much faster and more aggressively than before. This makes sense when you consider it from the PoV of the platforms (they have much more content to choose from)

A very in-depth tool that acts as a easily browse-able reference to many Apache Kafka internals like configuration options, error types, the wire format (by version), config advice and version upgrade diffs.

They make $8-9B a year (~90% profit margins) selling software to mainframes, which were deployed ages ago but still have to be maintained because critical COBOL business code was written on their systems - and migration is too riskly/costly.

To give you an idea:

- of the risk in regulated industries like banking: a UK bank was once fined *$62 million* for botching a mainframe migration and causing downtime. - of the difficulty and risk in non-tech industries: Australia once spent *$120 million* trying to migrate its social security system off mainframes... and failed.

Mainframes are not their only business, of course, but it's a major cash cow that's under appreciated. I, for one, didn't know that business keeps growing.

Coincidentally, I wrote about the topic of mainframes with relation to IBM's acquisition of Confluent here today: https://blog.2minutestreaming.com/p/ibm-confluent-acquisitio...

exactly. i posted about the same thing today https://x.com/twitter/status/2025949280251597291

It's an accelerant, both good and bad. How that plays out in companies where the majority are below-average is a nuanced and concerning case

I think it's worth it to build your own miniaturized versions of OpenClaw/claw-like agents. It's easy enough to build and the confidence of it being in a language you're familiar with, small enough surface area to limit risk, etc. seems worth it imo

In a way I think handing off digital tasks to an AI bot that does it behind the scenes IS reducing technology in your life.

But has to be done carefully to not increase the scope of things being done