SaaS Infrastructure
Multi-Tenant Data Access & Job Infrastructure
Tenant-scoped data access and Bull/BullMQ + Redis job infrastructure powering scheduled and event-driven patient outreach for multiple hospitals.
- Node.js
- MongoDB / Mongoose
- Redis
- Bull / BullMQ
- Auth0
- JWT
The problem
Bursts of EHR events and messaging campaigns from many hospitals had to be processed without cross-tenant leakage or duplicate sends.
What I built
Data-access patterns that scope every query, job payload, and cache key to a hospital, plus idempotent jobs on tenant-partitioned Redis queues.
My role
- Designed multi-tenant data access patterns
- Built background job infrastructure
- Idempotent job design
- Auth0 / JWT validation
Technical highlights
- Tenant scope checked in the data-access layer, never trusted from the caller
- Tenant-partitioned queues: one hospital's burst can't affect another's patients
- Idempotent jobs: retries never double-send a message