> whoami
Rehber Moin
$ focus:
I build the infrastructure behind trade execution at BlackRock - platforms processing $5-10B/day in SWIFT transactions across $1T AUM. Apache Kafka, gRPC, Redis, Apache Ignite.
Author of RiptideKV (a Redis-compatible KV store from scratch in Rust). Currently teaching System Design at Scaler Academy.
Yes, I built my portfolio as a distributed system. No, I will not apologize.
statusopen to conversations
locationGurugram, IN 🇮🇳
experience2+ years
caffeine level▓▓▓▓▓▓░░ 75%
currently
cat ~/.nowworking on
Cachematrix platform at BlackRock - $5-10B/day SWIFT
building
RiptideKV - Redis-compatible KV store from scratch (Rust)
teaching
System Design (LLD, HLD) at Scaler Academy
obsessed with
Exactly-once semantics in Kafka
listening to
lo-fi beats to deploy to
thinking about
Cache-aside vs read-through at scale
r3hbr@cluster ~ neofetchview dotfiles →
╔══╗ ║R3║ ║HB║ ║R ║ ╚══╝
r3hbr@infrastructure
─────────────────────
role ~ Backend Platform Engineer
company ~ BlackRock
stack ~ Java · Rust · TypeScript
infra ~ Kafka · Redis · gRPC · Ignite
editor ~ Neovim (btw)
shell ~ zsh + starship
os ~ macOS · Arch Linux
// latest
SHIPproject · actively shipping
RiptideKV v5.0 - Redis-compatible KV store (Rust)
POSTblog · technical writing
Java Internals & Distributed Systems
PUSHwork · production
feat: exactly-once Kafka pipelines at BlackRock
┌───────────────────┐ │ │ │ systems are just │ │ people problems │ │ in disguise │ │ │ │ - r3hbr │ └───────────────────┘
System Topology
$kubectl get topology / r3hbr-infrastructure│nodes: 9edges: 9all healthy
click node to navigate • drag to pan • scroll to zoom
// philosophy.yml
Systems over features
I don't build apps. I build the infrastructure that apps depend on. The best code I write is the code you'll never see - until it stops running.
Fail fast, recover faster
Every system fails. The question is whether you built it to crash gracefully at 3am without waking anyone up. That's the actual engineering.
Complexity is debt
If I can't explain the architecture on a napkin, it's wrong. The hardest engineering is making complicated things simple - not the other way around.