» Tag
backend
36 postsManaging User Data in Globally Distributed Web Architectures
A look at how multi-region architectures balance latency, consistency, and data residency for global-scale web applications.
Engineering webhooks that never get lost: queue, retry, idempotency
A practical breakdown of reliable webhook delivery architecture: fast ack, queuing, idempotency, exponential backoff, dead letter queues and replay for payment integrations.
Streaming LLM Responses in Django and React: A Practical Guide
A practical guide to streaming LLM responses in Django with Server-Sent Events, covering React integration, Gunicorn workers, Nginx buffering and Celery.
CommitBrief — AI code reviews, right in your terminal
A provider-agnostic, local-first CLI that reviews your staged changes, a historic range, or a whole GitHub pull request. Zero telemetry, no server. Free and open source.
commitbrief.comSupabase vs Firebase: Choosing Your Backend Stack
A practical comparison of Supabase's Postgres foundation and Firebase's Firestore model, covering vendor lock-in, pricing, offline support, and scaling trade-offs.
Request Logging: Tracing Production Requests with Correlation IDs
Why correlation IDs and structured logs are essential for request logging. A practical look at Fastify, Express, pino, and AsyncLocalStorage for production debugging.
The Serverless CPU-Throttling Bug That Freezes Background Tasks
Cloud Run's request-based CPU model freezes background tasks scheduled after a response, causing jobs to hang for minutes or vanish. Cause, diagnosis and fix.
Fixing Postgres RLS Recursion with a JWT Custom Claims Hook
A single GRANT line triggered an infinite RLS recursion (42P17) in Postgres. How moving role checks out of user_roles into a signed JWT claim fixed it—and its trade-offs.
Why Midnight Billing Cron Jobs Break at Scale
Why midnight subscription billing cron jobs collapse at scale, and how to fix them in Laravel with queues, idempotency, and staggered renewal windows.
Why LLM Apps Must Be Engineered as Distributed Systems
A production AI app broke under load—not because of the model, but missing queues, caching, retries and observability. Backend engineering is the real differentiator.
PostgreSQL Batch UPSERT with CTE: From 90 Seconds to 5
An email sync process with audit history was rewritten from separate queries into a single PostgreSQL CTE, cutting 100k-row processing time from 90 seconds to 5.