APIs, GraphQL, microservices, and server-side engineering.
13 articles in this category
A hashed password still shouldn't leave your API. class-transformer's @Exclude and @Expose decorators make an entity define what's safe to serialize, instead of trusting every controller to filter it manually.
Vanshit Patel
High-read endpoints were re-running the same database joins on every request, pushing response times to 150-250ms. Here's how a cache-aside Redis layer cut that to single-digit milliseconds.
Vanshit Patel
A messy backend structure doesn't just look bad — it slows down debugging, onboarding, and scaling. Here's how reorganizing folders into Core, Config, Module, and Shared layers changed both.
Vanshit Patel
Cypress runs inside the browser instead of driving it remotely, which is why its automatic waiting kills flaky tests instead of just hiding them. Speed and stability aren't a tradeoff — they're the same investment.
Vanshit Patel
A lint-test-build-push pipeline for a NestJS backend caught a Joi schema bug that never showed up locally, because a .env file was quietly masking it. Docker and CI, run together, close that gap.
Vanshit Patel
Dashboards look like a frontend problem until a month with zero data breaks your growth math. How PostgreSQL window functions and careful edge-case handling keep the numbers trustworthy.
Vanshit Patel
Password forms are a liability for users and developers alike. How OAuth's authorization-code flow, provider trust, and stateless JWTs replace stored credentials entirely.
Vanshit Patel
REST struggles as systems scale. See how GraphQL with Apollo collapses many endpoints into one flexible query layer for microservices.
Vanshit Patel
Cart-level coupons are easy to abuse and hard to analyze. A three-table schema — coupons, product rules, and a usage log — makes discounts product-aware and auditable.
Vanshit Patel
Product variants look like a simple one-to-many relationship — until they touch every module. Lessons from restructuring Product, Cart, and Order schemas around a single source of truth.
Vanshit PatelBackend projects rarely fail on day one — they fail slowly. The real culprits: missing architecture boundaries, weak error handling, over-trusted auth, and zero observability.
Vanshit Patel
Hitting "Send" and eyeballing a 200 isn't testing. How Postman's Tests tab — environment variables, status assertions, and data integrity checks — turns a collection into living documentation your team can trust.
Vanshit Patel
Two users buying the last unit of the same variant at once shouldn't oversell your stock. How database transactions and row-level locking closed that race condition.
Vanshit Patel