
Founder & CEO @LaserDataInc | ex-@Apple | Advisor @DialpadHQ | @ApacheIggy PMC Chair
San Francisco
Joined March 2010
- Tweets203
- Following51
- Followers81
- Likes142
Pinned Tweet
Models made intelligence cheap. Agents are going to make data movement and state management expensive.
Agents are constantly reading context, changing state, calling tools, generating events, and handing work to other agents.
We spent the last few years figuring out how to run models efficiently. I strongly believe the next big infrastructure problem is going to be everything happening between them.
youtube.com/watch?v=mTGwnrfq…
We need a token refund policy for AI apologies. If the agent ignores instructions and I have to correct it, I shouldn't be burning tokens to read "Apologies, I missed that!.." 💸🤖
Kranti Parisa retweeted
Fast is good. Predictably fast is what really matters!
What does it really take to achieve predictable P99 latency at scale?
At P99 CONF, our co-founder and CTO, @spetzu, shared the engineering decisions behind @ApacheIggy, a persistent streaming engine built from the ground up for ultra-low latency and high throughput.
Rust. Thread-per-core architecture. io_uring. Zero-copy optimizations. And a relentless focus on eliminating inefficiencies in the hot path.
The talk goes beyond benchmarks to explore how architectural choices translate into real-world performance.
At @laserdatainc, we believe the next generation of data infrastructure should deliver more throughput, predictable tail latencies, and dramatically better infrastructure efficiency.
That’s the philosophy behind Apache Iggy, and the foundation we’re building on.
Every millisecond counts. So does every byte.
youtube.com/watch?v=2j6BzKaO…
#ApacheIggy #P99CONF #Rust #DistributedSystems #LaserData
Performance is measured. Correctness is challenged. Failures are reproducible.
Outperforming Kafka in benchmarks means little if the engine can’t hold up when things go wrong.
There’s a lot of serious systems engineering behind those few milliseconds we proudly publish in @ApacheIggy’s benchmarks.
At @laserdatainc, our engineers are investing deeply in deterministic simulation testing (DST), deliberately breaking things to uncover bugs before production does.
Our ambition? Build an insanely scalable streaming engine without compromising on tail latency, efficiency, cost, or correctness. That’s the bar we believe agentic workloads at massive scale will demand.
We’re just getting started. Plenty of hard engineering ahead! 🚀
Don’t just take our word for it. Run Apache Iggy in VSR cluster mode. Push it. Break it. Tell us what you find.
Join us on Discord: discord.gg/apache-iggy
Or reach out: [email protected]
We’d love to see what breaks. ❤️
#ApacheIggy #Kafka #DistributedSystems #Rust #Onward #Upward
New on the blog: part 3 of 3 on Apache Iggy clustering. A deterministic simulator runs the whole cluster on one thread from a single seed, injects crashes, partitions and torn writes, and replays every bug.
iggy.apache.org/blogs/2026/1…
#iggy #asf #vsr #cluster #dst #rust #streaming
Making AI agents reliable is only half the problem. Making that reliability fast, predictable, and economically viable at scale is the other half.
We’re heading toward millions of concurrent agent sessions. Agents communicating, failing, recovering, and handing off work. Every interaction generating events that need to be persisted, processed, and sometimes replayed.
Why should durability come at the cost of latency? Why should reliability require an expensive infrastructure footprint?
You can build agent infrastructure on top of existing data infrastructure. Many teams are doing exactly that. But if we’re rethinking how software works with AI agents, shouldn’t we rethink the data infrastructure underneath them?
That’s the challenge we’ve taken on at LaserData.
Every millisecond counts. So does every dollar spent moving and persisting data.
Curious how others are tackling durability, tail latency, and infrastructure costs as agent workloads scale.
We put a chaos monkey in a multi-agent support desk and let it kill agents mid-run.
The replacement agents replayed the session from the stream, resumed from the last checkpoint, and didn't issue the refund twice.
Agents fail. Their sessions shouldn't.
laserdata.com/blog/agents-fa…
#agentiai #aidatainfrastructure #apacheiggy #laserdata #durableagentsessions
At 800MB/second, Persisted to disk: P99 @ 3ms. P99.9 @ 4ms. We're beating our own numbers!
And we haven’t even implemented Direct I/O yet.
Hell yeah!! 🚀
We've been cooking. Multi-leader clustering is coming to Apache Iggy, with every node leading its own partitions.
3-node cluster at 800 MB/s: p999 down 93% replicated, 87% persisted, +42% producer throughput.
github.com/apache/iggy
#iggy #asf #rust #streaming #performance
Kranti Parisa retweeted
Jordan Epstein: Ouch, you didn’t like my name? 🥲
I thought I had a pretty cool one!
Iggy = Italian Greyhound. One of the fastest dogs in the world. 🐕⚡
Fast dog. Fast streaming engine. Now does the name make a little more sense? 😄
lnkd.in/p/gWw8x8Rc
This one made me smile. 🙂
Interesting to see @ApacheIggy contributors/engineers being approached to help “shape the future of Kafka.” Meanwhile, the Iggy community is busy refining what the future of message streaming engines should look like.
Rust. Modern I/O. Predictable tail latency. Multi-protocol by design. Developer experience from day one.
All respect to Kafka and everything it has done for distributed systems and data streaming. And inspiring us in many ways!
Back to building!
#ApacheIggy #Rust #Kafka #Streaming #OpenSource
Kranti Parisa retweeted
Apache Iggy just hit 5000 stars on GitHub! Thank you to our 140+ contributors and everyone who starred, built, and contributed.
github.com/apache/iggy
#iggy #asf #apache #rust #oss #streaming #messaging #github
Kranti Parisa retweeted
New on the blog: part 1 of 3 on how Apache Iggy became a cluster. Why Viewstamped Replication Revisited over Raft, one VSR group per partition, how we swapped the whole server, and what it costs, with benchmarks.
iggy.apache.org/blogs/2026/0…
#iggy #asf #vsr #cluster #rust #streaming
Agents need Meta-Harness & Real-time Data. Come say hi at booth #754 on Level 2. We’re sharing the space with our friends at @RocketRideAI 🚀
Join us at @WeAreDevs World Congress North America in San Jose, September 23–25. We’re looking forward to three days of knowledge sharing, good conversations, and time with the people building what’s next.
One question we’d like to explore together: when an agent fails halfway through a task, what survives? At @laserdatainc, we’re building durable agent sessions on an append-only log powered by @ApacheIggy, so agents can replay and resume while other systems read the same stream.
If you’re working on agent recovery, handoffs, or real-time data, come compare notes. Find us on Level 2 at booth #754, sharing the space with our friends at RocketRide.
Full agenda in the comments below 👇
#RealTime #DataStreaming #AIDataInfrastructure #OpenSource #WeAreDevelopers #RustyRose
In the AI era, we talk a lot about models, agents, and intelligence. But underneath all of it, data still has to move, persist, replicate, and recover, fast and predictably. Apache Iggy 0.9.0 is a major step forward. 🚀
Clustering is here, built around Viewstamped Replication Revisited (VSR). And we’re doing it while staying focused on the thing Iggy has cared about from day one: predictable tail latency.
On a 3-node AWS i4i cluster at 800 MB/s:
Producer, replicated: ~3 ms p99
Producer, persisted to disk: ~7 ms p99
Warm consumer: <1 ms p99
I’m incredibly proud of what the Apache Iggy community has built. More than 60 contributors and 600+ merged PRs went into this release, including 34 first-time contributors. Thank you to everyone who wrote code, reviewed PRs, tested releases, reported issues, challenged assumptions, and helped move the project forward.
And we’re not settling here!
There are already further performance optimizations underway for 0.9.1. The goal isn’t simply to make Iggy fast. It’s to keep asking how much latency, overhead, and infrastructure we can eliminate while preserving durability and correctness.
Modern AI infrastructure deserves a streaming engine designed with modern systems engineering.
Congratulations, @ApacheIggy community. Onward. 👏
#ApacheIggy #MessageStreaming #AIDataInfrastructure
Apache Iggy 0.9.0 is out, our first release as a Top-Level Project! ⚡
Clustering has landed. Powered by Viewstamped Replication Revisited (VSR). 600+ PRs. 60 contributors, 34 of them new. Message streaming at laser speed, now highly available.
iggy.apache.org/blogs/2026/0…
#iggy #asf
Thank you @jamesacowling and Barbara Liskov for such an inspiring paper on VSR! dspace.mit.edu/entities/publ…
Read the release blog and check out what’s coming in 0.9.1
iggy.apache.org/blogs/2026/0…
So while @Apple starts its next chapter, we’re starting one of our own, for real-time streaming and agent data infrastructure.
September 9 will be a special day for @laserdatainc too.
One more stream is here. 💚
#LaserData #AIDataInfrastructure #DataStreaming #AGDXProtocol #LaserSDK
One more stream is here. 💚
Today marks the beginning of a new chapter for @laserdatainc
We’re bringing together three worlds that have largely evolved independently:
1. Real-time message streaming.
2. Agent Data Fabric.
3. Real-time applications.
One infrastructure. One durable foundation.
Today we’re announcing major new capabilities across the stack, from VSR-based clustering in @ApacheIggy and Agent Data Exchange (AGDX) Protocol for agent-agent-system data exchange, to new LaserData Cloud plans (launch, scale, performance, and enterprise) and deployment options across AWS and GCP.
All these capabilities are in PRIVATE BETA, will be GA on September 18, 2026.
And we’re just getting started.
We’ll continue shipping throughout the year. But once in a while, we’ll take a moment to bring together the biggest ideas we’ve been working on and share where we’re taking real-time and agent data infrastructure next.
Welcome to the next chapter of LaserData. 🚀
Read the blog about our Data Streaming Infrastructure for the Agent Era laserdata.com/blog/data-stre…
Kranti Parisa retweeted
One more stream is here. 💚
Today marks the beginning of a new chapter for @laserdatainc
We’re bringing together three worlds that have largely evolved independently:
1. Real-time message streaming.
2. Agent Data Fabric.
3. Real-time applications.
One infrastructure. One durable foundation.
Today we’re announcing major new capabilities across the stack, from VSR-based clustering in @ApacheIggy and Agent Data Exchange (AGDX) Protocol for agent-agent-system data exchange, to new LaserData Cloud plans (launch, scale, performance, and enterprise) and deployment options across AWS and GCP.
All these capabilities are in PRIVATE BETA, will be GA on September 18, 2026.
And we’re just getting started.
We’ll continue shipping throughout the year. But once in a while, we’ll take a moment to bring together the biggest ideas we’ve been working on and share where we’re taking real-time and agent data infrastructure next.
Welcome to the next chapter of LaserData. 🚀
Some @Apple habits are worth keeping, and launch days still feel special. We have something to share too. 😊
Connecting a LangChain agent to Sail is now just one install.
docs.lakesail.com/sail/lates…



















