API design & build
REST or GraphQL APIs in Node.js and TypeScript, with validation, auth and tests.
Service · Node.js backend, APIs & performance
Node.js backend development that holds up in production.
Most of my work is backend: APIs, data models, event-driven services and the performance work that keeps them fast, in systems where a slow query or a duplicated event costs real money.
- Node.js
- TypeScript
- Express
- GraphQL
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Apache Kafka
- Grafana
- Jest
01 — The problem
Where backends slow down.
Products rarely get slow all at once. A missing index, a query inside a loop, a report that runs on the request thread, a webhook that isn't idempotent: each is harmless at launch and painful at ten times the data.
I measure before changing anything, fix the few things that account for most of the time, and prove each one with before-and-after numbers, so you know what every fix was worth.
02 — What you get
What you get.
Data modelling
Schemas and migrations in PostgreSQL, MySQL or MongoDB, designed around how the data is queried.
Query & cache tuning
Indexing, query rewrites and Redis caching, measured before and after.
Event-driven services
Kafka consumers and producers with idempotent handlers, retries and dead-letter queues.
Architecture review
A written, prioritised report on what is slow, what is risky and what to fix first. Fixes on request.
Observability
Logs, metrics and Grafana dashboards that catch anomalies before your users do.
03 — Process
How a project runs.
One point of contact, from planning to a deployed product your team owns.
01
Measure
Profile the real workload: slow queries, hot endpoints, queue lag and error rates.
02
Prioritise
Rank fixes by time saved and risk, and agree which ones are worth doing.
03
Fix & prove
Ship each fix behind tests, with before-and-after numbers.
04
Keep it fast
Dashboards and alerts so a regression is caught the day it ships.
04 — Proof
Work that shows it.
Products I've designed, built and run myself. Each has a full case study.
Theliv — AWS cost-monitoring SaaS
Nightly ingestion across every connected AWS account, per-account spike detection, and a savings ledger that credits each saving exactly once, enforced in the database.
Read the case studyDryDock Kit — multi-tenant SaaS starter
Idempotent payment webhooks for four providers, seat limits that hold under a concurrent race, and integration tests against a real PostgreSQL database.
Read the case study05 — Who it's for
A good fit if you are…
Products whose API or database has slowed down as data grew.
Teams about to scale who want the risky parts found first.
Startups that need a backend or API built for an existing frontend or mobile app.
06 — FAQ
Before you get in touch.
Can you review our backend without building anything?
Yes. The architecture review is a fixed deliverable on its own: a written, prioritised report. You can have me implement the fixes, or hand it to your team.
Which databases do you work with?
PostgreSQL, MySQL and MongoDB in production, with Redis for caching.
Do you work alongside an existing team?
Yes. I lead an engineering team in my full-time role, so code review, pairing and written design docs are part of how I work.
08 — Contact
Let's Build Something.
I take on a small number of projects at a time, from full product builds to deployment, performance and automation work: scoped, shipped, and handed over clean.
Bengaluru, India → Open to RelocationReplies under 24h