stack → Go · gRPC · Kafka · RabbitMQ · PostgreSQL · Redis · Docker
build → Distributed Systems · Event-Driven Architecture · Microservices
focus → Reliability Engineering · Fintech Infrastructure
method → First principles. Understand the why before the how.I build backend infrastructure.
The kind that processes payments, delivers webhooks, moves events between services, and keeps working when things fail.
I'm interested in distributed systems, event-driven architecture, and designing software that's reliable, scalable, and easy to reason about.
💸 PayoutX
Production-inspired payout infrastructure with reliable event processing.
Go · gRPC · Kafka · PostgreSQL
💳 FlowPay
Distributed payment system built around event-driven architecture.
Go · gRPC · Kafka · PostgreSQL
Asynchronous webhook delivery platform powered by RabbitMQ and worker pools.
Go · RabbitMQ · PostgreSQL
Low-latency URL shortener with Redis caching and clean layered architecture.
Go · Redis · PostgreSQL
🚦 HoldUp
Token bucket rate limiter implemented as reusable Go middleware.
Go
These are the ideas I keep coming back to.
- Idempotency
- Event-Driven Architecture
- Transactional Outbox
- State Machines
- Retry Strategies
- Dead Letter Queues
- Worker Pools
- Graceful Shutdown
- Context Cancellation
- Backpressure
- Caching
- Clean Architecture
- Observability
- Docker-first Development
- Distributed Systems
- Fintech Infrastructure
- System Design
- Kafka Internals
- Database Design
- Go Performance
- Reliability Engineering
Most backend bugs aren't caused by syntax.
They're caused by systems behaving differently than we expected.
I enjoy building software that remains predictable when networks fail, workers crash, APIs timeout, or messages are delivered more than once.
Good backend engineering isn't about writing clever code—it's about designing dependable systems.
"Build simple systems. Make them reliable. Scale them when necessary."