Skip to content

Upcoming Topics

Backend engineering doesn't end at REST APIs and PostgreSQL — there's a whole ecosystem of patterns , protocols , and platforms that separate "I can build an API" from "I can design distributed systems." These aren't academic exercises , every topic here solves a real problem you'll hit when your monolith starts feeling tight , your WebSocket connections pile up , and someone asks "should we use GraphQL?" in sprint planning

7 files covering the advanced patterns you'll need as your backend grows beyond CRUD

what you'll find here

  • GraphQL — Schema design , resolvers , subscriptions , security (depth limiting , auth , batching attacks)
  • WebSockets — Persistent bidirectional channels , scaling 10k concurrent connections , pub/sub patterns
  • Microservices — Service decomposition , inter-service communication , distributed systems nightmares
  • Serverless — Lambda functions , event-driven architecture , cold starts , stateless design constraints
  • Message Queues — Async job processing , RabbitMQ , Bull , queue patterns
  • What's Next — Bun , Deno , Edge computing , WebAssembly , CRDTs , AI integration

prerequisites

DevOps , Node.js , and Express sections — you should be deploying apps before you try distributed systems

first topic -> upcoming_00_home.md