Ted Naleid
@ted.naleid.com
Reposted by Ted Naleid
Excellent analysis from @vanlightly.bsky.social: A Fork in the Road: Deciding #ApacheKafka’s Diskless Future jack-vanlightly.com/blog/2025/10...
October 23, 2025 at 3:07 PM
Excellent analysis from @vanlightly.bsky.social: A Fork in the Road: Deciding #ApacheKafka’s Diskless Future jack-vanlightly.com/blog/2025/10...
Reposted by Ted Naleid
New post: why I’m not a fan of “zero-copy” Iceberg tables for Apache Kafka.
From a systems design view, it trades storage savings for coupling and complexity.
Sometimes, duplication is cheaper than coupling.
jack-vanlightly.com/blog/2025/10...
From a systems design view, it trades storage savings for coupling and complexity.
Sometimes, duplication is cheaper than coupling.
jack-vanlightly.com/blog/2025/10...
Why I’m not a fan of zero-copy Apache Kafka-Apache Iceberg — Jack Vanlightly
Over the past few months, I’ve seen a growing number of posts on social media promoting the idea of a “zero-copy” integration between Apache Kafka and Apache Iceberg. The idea is that Kafka topics cou...
jack-vanlightly.com
October 15, 2025 at 1:39 PM
New post: why I’m not a fan of “zero-copy” Iceberg tables for Apache Kafka.
From a systems design view, it trades storage savings for coupling and complexity.
Sometimes, duplication is cheaper than coupling.
jack-vanlightly.com/blog/2025/10...
From a systems design view, it trades storage savings for coupling and complexity.
Sometimes, duplication is cheaper than coupling.
jack-vanlightly.com/blog/2025/10...
Cloudflare is doing a lot of interesting work (R2 object store, cloudflare workers, pay-per-crawl for LLMs). They annouced Cap'n Web, a new RPC system that works on all JS runtimes. One of its biggest innovations over REST/GraphQL is "promise pipelining" blog.cloudflare.com/capnweb-java...
Cap'n Web: A new RPC system for browsers and web servers
Cap'n Web is a new open source, JavaScript-native RPC protocol for use in browsers and web servers. It provides the expressive power of Cap'n Proto, but with no schemas and no boilerplate.
blog.cloudflare.com
September 23, 2025 at 10:57 PM
Cloudflare is doing a lot of interesting work (R2 object store, cloudflare workers, pay-per-crawl for LLMs). They annouced Cap'n Web, a new RPC system that works on all JS runtimes. One of its biggest innovations over REST/GraphQL is "promise pipelining" blog.cloudflare.com/capnweb-java...
> The people succeeding with AI aren’t the ones who suddenly discovered taste. They’re the ones who already had it and simply adapted their standards to a new tool. Develop your taste with or without AI. The medium doesn’t matter, the fundamentals do.
matthewsanabria.dev/posts/you-ha...
matthewsanabria.dev/posts/you-ha...
You Had No Taste Before AI
The bitter truth about people preaching taste with AI.
matthewsanabria.dev
September 18, 2025 at 3:55 PM
> The people succeeding with AI aren’t the ones who suddenly discovered taste. They’re the ones who already had it and simply adapted their standards to a new tool. Develop your taste with or without AI. The medium doesn’t matter, the fundamentals do.
matthewsanabria.dev/posts/you-ha...
matthewsanabria.dev/posts/you-ha...
good post on Kakfa + Iceberg from the WarpStream folks: www.warpstream.com/blog/the-cas...
Most implementations gloss over the difficulties in iceberg table maintenance, and the only solution that the marketplace seems to have is Spark. Great if your team has Spark already, but painful otherwise.
Most implementations gloss over the difficulties in iceberg table maintenance, and the only solution that the marketplace seems to have is Spark. Great if your team has Spark already, but painful otherwise.
The Case for an Iceberg-Native Database: Why Spark Jobs and Zero-Copy Kafka Won’t Cut It
We launched a new product called WarpStream Tableflow that is the easiest, cheapest, and most flexible way to convert Kafka topic data into Iceberg tables with low latency, and keep them compacted.
www.warpstream.com
September 17, 2025 at 5:24 PM
good post on Kakfa + Iceberg from the WarpStream folks: www.warpstream.com/blog/the-cas...
Most implementations gloss over the difficulties in iceberg table maintenance, and the only solution that the marketplace seems to have is Spark. Great if your team has Spark already, but painful otherwise.
Most implementations gloss over the difficulties in iceberg table maintenance, and the only solution that the marketplace seems to have is Spark. Great if your team has Spark already, but painful otherwise.
Love this Blindsight metaphor for directly sharing AI-slop output to others
It’s rude to show AI output to people
It's rude to show AI output to people | Alex Martsinovich
Feeding slop is an act of war
distantprovince.by
August 2, 2025 at 3:42 PM
Love this Blindsight metaphor for directly sharing AI-slop output to others
Submitted a talk to Current '25 New Orleans (in October): "The Rise of Object Store Architectures: Understanding SlateDB"
SlateDB is an object-store backed LSM tree storage engine and is a building block for cloud native architectures. It's a useful lens for understanding the architectural shift.
SlateDB is an object-store backed LSM tree storage engine and is a building block for cloud native architectures. It's a useful lens for understanding the architectural shift.
June 15, 2025 at 2:16 AM
Submitted a talk to Current '25 New Orleans (in October): "The Rise of Object Store Architectures: Understanding SlateDB"
SlateDB is an object-store backed LSM tree storage engine and is a building block for cloud native architectures. It's a useful lens for understanding the architectural shift.
SlateDB is an object-store backed LSM tree storage engine and is a building block for cloud native architectures. It's a useful lens for understanding the architectural shift.
"We all used to believe that changing passwords often was a good idea; turns out the opposite is true. Similarly, we all used to believe that making people log in frequently was good security. ... Except, well, that’s not how anything works."
tailscale.com/blog/frequen...
tailscale.com/blog/frequen...
Frequent reauth doesn't make you more secure
Securely connect to anything on the internet with Tailscale. Built on WireGuard®️, Tailscale enables you to make finely configurable connections, secured end-to-end according to zero trust principles,...
tailscale.com
June 14, 2025 at 2:28 PM
"We all used to believe that changing passwords often was a good idea; turns out the opposite is true. Similarly, we all used to believe that making people log in frequently was good security. ... Except, well, that’s not how anything works."
tailscale.com/blog/frequen...
tailscale.com/blog/frequen...
Reposted by Ted Naleid
How to reliably distribute work across microservices, stream processors, durable execution, event-driven, orchestration and now AI agents?
Coordinated Progress is a 4 part series that explores the common structure behind reliable distributed systems.
jack-vanlightly.com/blog/2025/6/...
Coordinated Progress is a 4 part series that explores the common structure behind reliable distributed systems.
jack-vanlightly.com/blog/2025/6/...
Coordinated Progress – Part 1 – Seeing the System: The Graph — Jack Vanlightly
At some point, we’ve all sat in an architecture meeting where someone asks, “ Should this be an event? An RPC? A queue? ”, or “ How do we tie this process together across our microservices? Should it ...
jack-vanlightly.com
June 11, 2025 at 2:29 PM
How to reliably distribute work across microservices, stream processors, durable execution, event-driven, orchestration and now AI agents?
Coordinated Progress is a 4 part series that explores the common structure behind reliable distributed systems.
jack-vanlightly.com/blog/2025/6/...
Coordinated Progress is a 4 part series that explores the common structure behind reliable distributed systems.
jack-vanlightly.com/blog/2025/6/...
Reposted by Ted Naleid
An increasingly common conflict I am hearing:
"Our company evaluated using {advanced AI coding product}. But we found it too expensive compared to GitHub Copilot.
So we are staying on Copilot and our platform team is building our own custom AI tools on top of open source"
"Our company evaluated using {advanced AI coding product}. But we found it too expensive compared to GitHub Copilot.
So we are staying on Copilot and our platform team is building our own custom AI tools on top of open source"
June 8, 2025 at 2:28 PM
An increasingly common conflict I am hearing:
"Our company evaluated using {advanced AI coding product}. But we found it too expensive compared to GitHub Copilot.
So we are staying on Copilot and our platform team is building our own custom AI tools on top of open source"
"Our company evaluated using {advanced AI coding product}. But we found it too expensive compared to GitHub Copilot.
So we are staying on Copilot and our platform team is building our own custom AI tools on top of open source"