Designing Scalable Microservices in Node.js
A practical guide to service boundaries, contracts, and observability — designing Node.js microservices for a multi-vendor commerce platform.
Open to senior full-stack and backend roles
Building scalable systems, cloud-native applications, and high-performance digital products.
1.2M+
Events / Day
Redis Streams backbone I own
99.9%
Checkout Availability
multi-vendor commerce platform
-70%
p95 API Latency
queue-based re-architecture
20+
Systems Shipped
owned design → deploy → on-call
github.contribution_graph
last 6 months
01 · projects
Production systems with real constraints — select a card to inspect the problem, the architecture, and what it moved.
~/projects/multi-vendor-ecommerce
role: Backend owner — designed services, data model, and order pipeline
Problem
Independent vendors needed a single storefront with isolated catalogs, split payments, and per-vendor fulfillment — without the operational overhead of running separate stores.
Solution
Built a multi-tenant commerce platform with vendor onboarding, role-based dashboards, commission-aware checkout, and order routing that fans out a single cart to multiple vendors.
Architecture
Next.js storefront → Node.js/Express API gateway → MongoDB (tenant-scoped collections) with Redis for sessions and hot product cache; order events fan out through a queue to vendor services.
Key decision
Tenant-scoped MongoDB collections over one-database-per-vendor: same isolation guarantees at this scale, one connection pool, one backup story. Revisit at 1k+ vendors.
03 · experience
Commit history of a career — from research internships to owning production commerce systems.
2023 — Present
HEAD → mainBytive — multi-vendor commerce platform
2022
Daulat Ram College, University of Delhi
2021
Cluster Innovation Centre, University of Delhi
05 · blog
Writing up the systems I build — published on Medium. Queues, caches, auth, and the failure modes between them.
A practical guide to service boundaries, contracts, and observability — designing Node.js microservices for a multi-vendor commerce platform.
EC2, Lambda, S3 and beyond — the AWS services that carry real production workloads, and when to reach for each.
Replication, sharding, caching, and the trade-offs between them — a guide to scaling databases before they become the bottleneck.
Step-by-step HTTPS for EC2-hosted sites — free certificates with Certbot, auto-renewed by cron so they never expire in production.
Work and personal GitHub on one laptop without credential chaos — per-account SSH keys and config, done professionally.
Two-part series on production auth in Node.js — JWT access and refresh tokens, Joi validation, and security middleware in Express.
06 · contact
Hiring for a senior full-stack or backend role? Building something that needs to scale? Let's talk.
$ ssh vivek@available
Open to senior full-stack and backend roles. Fastest response over email — typically within 24 hours.
India · Remote-friendly
02 · architecture
Interactive diagrams of systems I've designed and run in production. Drag to pan, scroll the canvas with the controls.
diagram://ecommerce
Multi-vendor storefront: CDN-fronted Next.js, an API gateway fanning out to domain services, Redis hot cache, and queue-buffered order fulfillment.
04 · skills
Years and production context, not self-graded percentages — where each tool has actually shipped.
skill.radar()
Skill radar: Frontend 90 out of 100, Backend 92 out of 100, Cloud / AWS 82 out of 100, Databases 86 out of 100, System Design 84 out of 100, DevOps 80 out of 100.
production apps, App Router era
SSR/ISR storefronts, dashboards
strict mode, end to end
services handling 1.2M+ events/day
API gateways, auth, rate limiting
multi-tenant schemas, change streams
streams, caching, sessions — on-call for it
SQS · EC2 · S3 · Lambda in production
every service containerized
zero-downtime rollouts, 6-node fleet
service boundaries, contracts
idempotency, at-least-once delivery
DLQs, replay, backpressure