
engineering @hydra_db · go/rust engineer · fucking around and finding out
anywhere in the world
Joined May 2025
- Tweets10.9K
- Following555
- Followers2.1K
- Likes34.4K
finally a maintainer for github.com/hydra-db/hydradb 😍
[note to self]
at this point ive realized theres little to no point on posting your deep technical stuff on here, even if youre passionate about it, especially if your only goal on here is to build an audience and build distribution
tech stuff does get views, and im not denying that, but thatll always be a relatively smaller circle than the one youll build by simply posting absolute slop or just super generic stuff
as always, exceptions exist, but this is a very generalized thing which ive noticed
nice
aditya. retweeted
Andddd YellowBird Phase 2 is done, we completely migrated from images running in EC2 to Fargate + ECS clusters, have a separate repo with Terraform for ops, the app layer pushes SHA Docker image tags to ECR, and Fargate picks up the tags from it.
Migrated from a Cloudflare Tunnel between frontend and backend to frontend talking to Cloudflare DNS, which in turn talks to our load balancers and ACM, which forwards the traffic to the cluster.
S3 for images/videos with our own custom YellowBird VPC, a VPC endpoint for S3 Gateway. Migrated from RDS to Neon with pg_dump (RDS eats up a lot of credits). SSM parameters for secrets and CloudWatch for logs.
aditya. retweeted
the only moat is just doing it for the sake of doing it without asking anything in return
get my man employed asap (one of the few ppl from here who I can vouch for)
aight, fuck it, my turn for this kind of post
i'm looking for work.
i'm 21 and i've spent a rather unreasonable amount of time building software over the past year.
here's some of what i've been up to:
kiban: built an embedded LSM storage engine from scratch in rust. WAL, SSTables, compaction, snapshots, concurrency, crash recovery and fault injection.
the benchmarks are probably my favourite part. on warm 1M-record workloads, i got 0.96µs median point reads and over 1M point-read calls/s, with 2.2-2.7x faster point reads than tuned RocksDB. group commit pushed fully durable writes to 5,379/s at 16 writers, a 7.5x improvement. also managed to shrink the point index by 61%.
styx: a ~41k LOC bittorrent client in rust with 600+ tests. implemented peer-wire networking, verified downloading/seeding, trackers, DHT, magnet metadata exchange, daemon IPC, CLI/TUI and a desktop shell.
kurogane: implemented Raft consensus from scratch in rust. elections, log replication, snapshots, crash recovery, joint consensus, real gRPC networking and a deterministic fault-injecting simulator with linearizability verification.
konto: built a double-entry accounting engine with PostgreSQL and typescript. atomic transactions, holds, transfers, idempotency and enforced financial invariants. includes stress testing with 1,000 concurrent transfer/hold operations.
iris: built a GPU-accelerated image viewer for linux using rust, Vulkan, GTK4 and DMA-BUF. RAW decoding, ICC colour management, GPU rendering, Wayland presentation and software fallbacks.
webnotes: built a local-first notes app with a native Tauri desktop client, SQLite storage, bidirectional linking, a structured editor and web synchronization.
scribe: built an open-source publishing SDK for React, Next.js and Vite. handles Markdown/MDX compilation, typography, components, styling and local authoring. currently in public beta.
and then there's my open source work.
i've had PRs merged into HelixDB, Turso, Apache DataFusion, Zed, NativeLink, Zilliz Knowhere and Nix, covering everything from database internals and query execution to infrastructure, editor behaviour and correctness fixes.
i've also got contributions underway in RocksDB, Neon, HydraDB, FalkorDB and Starship, among others.
most of my work revolves around rust, typescript, databases, storage, networking and systems engineering. i've also been getting deeper into ML infrastructure and inference.
i'm looking for a full-time remote engineering role. internships and contracts are on the table too.
my github has all the code, benchmarks and documentation:
github.com/aetosdios27
if you're hiring or know someone who is, hit me up.
reposts appreciated :)
im excited to read this :)
After a year of quiet work, I'm ready to announce Egres.
Egres is a Postgres-compatible database designed to tackle heavy workloads and run thousands of tenants on the same server. It works with psql and drivers unchanged. The post covers the what, the why and the how:
manishrjain.com/egres/
For Egres, I wrote a new storage engine called zdb: a tree of LSM trees, which I call an LSM forest. It runs on local disk or object storage, has roaring bitmaps integration for indexing, and can do instant zero-copy branches of a database or a table.
Everything runs on zfiber, a coroutine system I wrote for Egres. It meters CPU ticks, disk IOPS and memory used per query, per tenant, so thousands of tenants can share the same server without the noisy neighbor problem.
This release is single node and the query features are very basic. Raft replication is already baked in. Future releases will allow multi-node clusters. Try it out! Would love to hear what you think.












