That's me. From being an ML Engineer to contributing to a DB project. Never imagined this timeline but here we go.

Build @measure_sh as an open source mobile app monitoring platform. Use @ApacheIggy for ingesting crazy amounts of mobile telemetry data. Run into issues. Iggy maintainer drops into our repo. Stress tests 3 million events. Tells us how to improve perf. Open source is ❤️

Apache Iggy just hit 100 contributors! Thanks to every one of you. The community keeps growing. github.com/apache/iggy #iggy #rust #apache #asf #messaging #streaming #opensource

Show, don't tell. Apache Iggy benchmarks - refactored, reproducible, and transparent. benchmarks.iggy.apache.org #iggy #rust #apache #asf #oss #streaming #messaging #benchmarks

Everywhere I go, people keep commenting on how wild it is that I have something working with us straight from *prison*. Well, no longer. Tomorrow, at 8 am in the morning, @PThorpe92 is a free man. Preston is an inspiration to us all. He achieved so much from behind bars. I am sure he will go even higher as a free man.

I'm extremely happy to announce that this year I'll have the chance to speak at the top-tier, performance-oriented #P99CONF 🚀

Same. Anyone in the DB space who might be looking to bring on an entry level DBMS developer with real open source experience on a greenfield DB, @pavan4820 is by far one of our most valuable contributors and has got us for thousands of dollars in rewards from the turso bug bounty

Every millisecond counts with @EigenVectorizer.

🚀 Apache Iggy 0.8.0 is out! Wire protocol rewrite, persistent WAL journal, new shard architecture, stronger security, SDK & connectors progress. Clustering keeps accelerating. iggy.apache.org/blogs/2026/0… #iggy #rust #io_uring #vsr #apache #asf #streaming

I wrote a little bit about how I've been designing my engine with zero-copy page access. Two problems to solve: - Copy at the OS boundary - Fresh copies from buffer pool into higher layers Thank you to @EigenVectorizer and @debasishg for reviewing a draft.

92% improvement in P9999 latency. 4 GB/s consumer throughput. One node. 🚀 How? By building @ApacheIggy entirely in Rust. Join @EigenVectorizer from @laserdatainc at #RustIndia2026 for a deep dive into: ✅ Why they swapped tokio_rs for io_uring ✅ Zero-copy serialization strategies ✅ Handling RefCell hurdles in async Rust ✅ The move to Viewstamped Replication (VSR) The schedule is officially LIVE! Grab your tickets! hasgeek.com/rustbangalore/ru… #rust #rustlang #RustIndia #conference #bengaluru #hasgeek

The full deck on Sid’s cancer approach is here: sytse.com/cancer/ Worth a read. Raw data for download is also available and linked in the deck

Rust is thriving at @TheASF 🦀 🥇 Apache DataFusion - 8.5k ⭐ 🥈 Apache OpenDAL - 5k ⭐ 🥉 Apache Iggy - 4.1k ⭐ The future of open-source data infrastructure is written in Rust. iggy.apache.org #Rust #OpenSource #Apache #DataEngineering #Streaming #Iggy

Compiler is correct 99.99% of the every time.

Happy to see that our recent blog post about thread-per-core & io_uring migration has been mentioned by @ThisWeekInRust this-week-in-rust.org/blog/2…

Thread-per-core io_uring? See how we moved Apache Iggy from Tokio's work-stealing to a shared-nothing* architecture to make the most out of modern hardware and provide ultra-low, predictable tail latencies. iggy.apache.org/blogs/2026/0… #io_uring #iggy #rust #streaming #apache #asf

Trying to squeeze 5GB/s from localhost has turned into a deep learning exercise. The best I'm getting is 1.5GB/s.

Performance Hints Over the years, my colleague Sanjay Ghemawat and I have done a fair bit of diving into performance tuning of various pieces of code. We wrote an internal Performance Hints document a couple of years ago as a way of identifying some general principles and we've recently published a version of it externally. We'd love any feedback you might have! Read the full doc at: abseil.io/fast/hints.html

The lack of "feature design" is why so many products over time feel hollow or messy. This isn't visual design. This isn't architectural design. I thought that a short video lecture of what feature design is and a real case study of applying it in Ghostty would be helpful. Feature design is the planning step behind how you're going to solve one or more user problems with a product feature: what that feature looks like, how it feels, and not just how its going to tactically solve these specific problems, but how that solution is going to interface with the edges of other features that currently exist or are planned to exist in the future.

Why you might want to consider the completion-based I/O (io_uring) for your next project. Check this discussion (a glimpse of the future blog post). reddit.com/r/rust/comments/1… #iggy #rust #io_uring #compio #tokio #apache #asf