Tag
132 articles tagged #Backend.
P.01Bun 1.3 ships Bun.sql, a unified client for Postgres, MySQL, MariaDB, and SQLite, plus a native Redis client Bun claims is 7.9x faster than ioredis. Here's the real API, working code, and when it's actually worth dropping your existing driver.
P.02Event sourcing stores every change to your data as an immutable event, then derives current state by replaying them, instead of overwriting a row each time something changes. Here's what that actually buys you, and the real operational cost it isn't worth paying in most systems.
P.03Hexagonal architecture keeps your business logic from importing your database driver, your HTTP framework, or your payment SDK. It also adds files and indirection you don't always need. Here's how it works, a working example, and how to tell if your project actually needs it.
P.04100% code coverage tells you every line ran during your tests. It says nothing about whether your tests would notice if that line broke. Mutation testing answers that question directly, here's how to run it with Stryker and mutmut and what to do with the score.
P.05Most teams reach for cache-aside by default and never ask if it's actually the right pattern. Here's how the three main caching strategies behave under real traffic, the consistency gap each one leaves open, and how to pick between them.
P.06CAP theorem gets summarized as 'pick two of three' so often that the summary has replaced the theorem. Here's what it actually says, why the real constraint only bites during a network partition, and how to pick a consistency model for a system you're actually building.
P.07In under three months, one developer rebuilt Postgres from scratch in Rust using AI coding agents, and pgrust now matches Postgres 18.3's output across more than 46,000 regression queries. Here's what it actually is, and isn't, and why it matters.
P.08Deno Sandbox spins up isolated Firecracker microVMs in under 200ms for running code you don't trust, AI-agent output included. Here's how it works and a working example.
P.09Webhooks push data to you the moment something happens; polling has you ask repeatedly whether anything changed. Here's how to decide which fits your integration, plus real code for both and the hybrid pattern most production systems actually need.
P.10A distributed lock keeps two processes on different machines from touching the same resource at once, but the naive Redis implementation has a gap that lets it fail silently. Here's how the pattern actually works, and the fencing token that closes the gap.
P.11Round robin isn't wrong, but it's the wrong default more often than teams realize. Here's how the main load balancing algorithms actually behave under uneven traffic, when each one earns its complexity, and a working consistent hashing implementation.
P.12A naive retry loop can turn a brief blip into a full outage by hammering a recovering service the instant it comes back. Here's how exponential backoff and jitter actually prevent that, with working code, not just the formula.
P.13Sharding splits one database across many machines when a single server can't hold or serve your data anymore. The strategy you pick determines whether you get hot spots, painful resharding, or a system that actually scales. Here's how each one works.
P.14Queues, pub/sub, and event streaming all move messages between services, but they answer different questions about delivery, replay, and who's allowed to read what. Here's the decision framework and where each one breaks down.
P.15Writing to your database and publishing an event are two separate operations, and a crash between them silently loses data. The transactional outbox pattern closes that gap. Here's how it works and how to implement it.
P.16A single GraphQL schema works until multiple teams own different parts of your data. Here's what federation actually solves, how Apollo Federation composes subgraphs, and when the added complexity is worth it.
P.17Adding read replicas is the standard fix for a database under read load, but it introduces a gap between when data is written and when it's readable everywhere. Here's what replication lag actually does to your application and how to design around it.
P.18When a business transaction spans multiple services, you can't wrap it in one database transaction anymore. The saga pattern solves this with a chain of local transactions and compensating actions. Here's how it works and when it earns its complexity.
P.19A growing thread of developer discussion is pushing back on fashion-driven stack churn, favoring Rails, Elixir, and calmer backend systems over the next new framework. Here's why boring is winning arguments it used to lose, and when it's still the wrong call.
P.20Idempotency keys let a client safely retry a request that might have already succeeded, without double-charging a card or double-creating an order. Here's how the pattern works, with a real implementation against Postgres and Redis.
P.21CQRS separates the code path that changes data from the code path that reads it. It solves real scaling and modeling problems, and it's also one of the most over-applied patterns in backend architecture. Here's when it earns its complexity.
P.22An N+1 query bug turns one page load into hundreds of database round trips. Here's what causes it, how to spot it in Django, Rails, and Prisma, and the eager-loading fixes that make it go away for good.
P.23OAuth handles authorization, OIDC adds identity on top of it, and SAML is the older enterprise SSO standard that still runs a lot of the corporate world. Here's how to pick the right one without reading three RFCs.
P.24PostgreSQL 19 Beta 1 shipped with a REPACK command that finally makes VACUUM FULL and CLUSTER safe to run without a maintenance window, plus parallel autovacuum and smarter async I/O. Here's what changed and what to test now.
P.25A circuit breaker stops your application from hammering a failing dependency until it recovers. Here's how the pattern works, the three states that make it up, and how to implement one without over-engineering a simple retry.
P.26FastAPI merged a significant router internals refactor on June 14, 2026, followed by app.frontend() for serving SPAs a week later. Routes are now preserved instead of cloned, dynamic route registration works, and serving a React or Vue frontend from FastAPI no longer requires a workaround.
P.27Node.js pushed security updates on June 18, 2026 across v22, v24, and v26, patching 12 CVEs. Two are high-severity auth bypasses. The most interesting is undici's HTTP response queue poisoning, which can send the wrong response to the wrong request on keep-alive connections.
P.28Deno 2.9 ships deno desktop — a way to turn any web project into a native, distributable desktop app with no Electron boilerplate. Here's what it does, what it's good for, and when to keep using Tauri or Electron instead.
P.29Database engineer is distinct from data engineer. One designs schemas, tunes queries, and manages production Postgres. The other builds pipelines. Here's how to hire the one who keeps your app fast.
P.30Phoenix LiveView is production-ready for real-time web applications. Here is what it enables, where it fits, and why teams choosing it are not making an exotic choice.
P.31C++ covers game engines, embedded systems, high-frequency trading, and infrastructure tools. The skills that matter are completely different depending on what you are actually building.
P.32Elixir's talent pool is small, opinionated, and genuinely skilled. Here is how to find the real engineers in it, what to test for, and why the screen differs from every other backend hire.
P.33Firebase's complexity and Supabase's Postgres assumptions do not fit every project. PocketBase, Appwrite, and Convex each solve the backend problem differently. Here is when each one makes sense.
P.34Both tools keep your dependencies current automatically. Here is how they actually differ, where each one breaks down, and which to choose based on your team's setup.
P.35Kotlin is the default language for Android and a growing choice for JVM backend work. This guide explains what to screen for, how Kotlin-specific skills differ from Java, and what the role actually requires.
P.36The .NET platform has changed more in the last three years than in the decade before. Here is what a strong .NET developer looks like today, what questions reveal real skill, and what separates modern .NET engineers from those still working in a 2015 mindset.
P.37Java 21 LTS brought virtual threads and pattern matching. Spring Boot 3 requires Java 17. Most job descriptions are still testing for Java 8. This guide covers what a strong Java developer looks like in 2026 and what questions reveal real skill.
P.38Laravel 12 is a very different framework than the one people picture when they dismiss PHP. This is a practical look at the stack, the tooling, and when an agency or product team should reach for it.
P.39Rails 8 changed the deployment and infrastructure story significantly. A developer who has kept up looks different from one working off 2019 knowledge. Here is what to screen for.
P.40Rust is growing fast in backend, systems, and WASM roles. Finding developers who actually understand ownership versus those who just fight the borrow checker is the whole challenge.
P.41Data engineers build the pipelines, warehouses, and transformation layers that make data useful. They are not data scientists, not backend developers, and not analysts. Here is how to hire for the actual role.
P.42Go powers Kubernetes, Docker, Prometheus, and half the cloud infrastructure tooling used by modern engineering teams. Hiring the right Go developer means understanding what the language attracts and what it demands.
P.43TypeScript is now the default for most web projects, which means the market is full of developers who write TypeScript without understanding it. Here is how to tell them apart.
P.44Node.js has fractured into async-first, TypeScript-native, and edge-runtime camps. This is the practical screening guide for hiring a Node.js developer who can build production backends, not just Express tutorials.
P.45LLM API bills grow faster than usage. These are the concrete techniques that cut costs by 40-80% without degrading quality: prompt caching, semantic deduplication, tiered model routing, and batch inference.
P.46Three tools, three different bets on where complexity belongs. Here's how to choose between BullMQ, Inngest, and Temporal based on what your system actually needs — not what sounds most impressive.
P.47OpenFeature is now a CNCF incubating project with broad SDK support. Here's how to use vendor-neutral feature flags in production — and why the standard matters more than the specific tool you back it with.
P.48Comparing LangSmith, Braintrust, and Weights & Biases Weave for LLM evaluation. What each platform does well, where it breaks down, and how to build a minimum viable eval pipeline.
P.49Durable Objects solve the coordination problem that makes edge computing hard: how do you maintain consistent state across distributed nodes? Here's how they work and when to use them.
P.50While the JavaScript ecosystem chased Bun, Deno, and edge runtimes, Fastify quietly became the production choice for high-throughput Node.js APIs. Here's why it's still the right call for many teams.
P.51Phoenix LiveView lets you build real-time, interactive UIs with server-side Elixir and minimal JavaScript. Here's how it works, where it shines, and what you give up compared to React.
P.52Kafka is the default answer for message queuing at scale. But for teams running fewer than a million messages per day, NATS JetStream offers persistence, delivery guarantees, and a dramatically simpler operational footprint.
P.53A practical guide to setting up metrics collection with Prometheus and visualization with Grafana for backend services — what to instrument, what to skip, and what the dashboards should actually show.
P.54Pydantic v2 shipped with a Rust-based core that made validation 5-50x faster. But the performance is only part of it — the v2 model redesign changes how you structure validation logic for complex APIs.
P.55async/await syntax makes Python code look concurrent. The behavior when you get it wrong is harder to predict than most tutorials explain. Here's what breaks in production and how to fix it before it does.
P.56The OWASP API Security Top 10 lists the most critical API vulnerabilities. Most are fixable with straightforward code changes. This guide walks through each one with real examples.
P.57A bloated Docker image costs you in pull times, storage fees, and attack surface. Here's how to build images that are small, fast to rebuild, and genuinely production-ready.
P.58Most web apps are missing four or five headers that would neutralize entire classes of attack. Here's what each header does, what to set, and why most defaults leave you exposed.
P.59Both frameworks can build RAG pipelines and agent systems, but they're designed with different priorities. Here's when to reach for each and when to skip both.
P.60Ollama makes it possible to run Llama 3, Mistral, Phi-4, and dozens of other open-weight models on your laptop or server with a single command. Here's what actually works and when local inference makes sense.
P.61R2's zero-egress pricing looks compelling on paper. Here's when it actually saves money, when S3's ecosystem still wins, and how to migrate if you decide to switch.
P.62Deno 2 ships with full Node.js compatibility, npm support, and a revised standard library. Here's what that means for teams evaluating it as a serious Node alternative.
P.63ElysiaJS gives Bun apps fast routing, request validation, and full type inference between server and client — without code generation. Here's how it works and when to use it.
P.64Logs tell you what happened. Error tracking tells you what broke, in what context, for which users. Here's how to set up Sentry properly and avoid the alert fatigue that makes it useless.
P.65ClickHouse is a columnar database designed for analytical workloads. It answers queries over billions of rows in seconds that would take minutes in Postgres. Here's what application developers need to know.
P.66dbt turns SQL SELECT statements into a tested, documented, version-controlled data pipeline. Here's how it works and when you should add it to your data stack.
P.67Vercel dominates frontend hosting. AWS dominates enterprise infrastructure. Between those two extremes, Fly.io and Railway are the most practical choices for backend-heavy full-stack apps in 2026.
P.68An Architecture Decision Record captures why a technical choice was made, not just what was decided. One page per decision, stored in the repo, reviewed in PRs. Here's the format and how to make it stick.
P.69Most background job solutions require you to run and monitor a Redis instance, manage worker processes, and wire up your own retry logic. Inngest skips all of that. Here's how it works and when it's the right call.
P.70Rails 8 ships Solid Queue, Solid Cache, Solid Cable, and Kamal 2. Together they make it possible to run a production app on one server, without Redis, without a separate Node process, and without external managed services for the basics.
P.71Bruno keeps API collections as plain files in your repository. No account, no cloud sync, no vendor lock-in. Here's how it compares to Postman and why teams are switching.
P.72Three headless CMS platforms used by agencies, three different bets on where content management is going. Here's how Sanity, Payload, and Contentful actually compare when you're building for clients.
P.73HTTP/3 replaces TCP with QUIC, a UDP-based protocol that eliminates head-of-line blocking and handles packet loss better. Here's when that matters, when it doesn't, and how to enable and verify it.
P.74Getting a language model to return reliably structured data is not just about asking nicely. Here's the pattern that actually works at production scale.
P.75MCP has become the standard for connecting AI models to external systems. Here's how it works, how to implement an MCP server, and what to watch out for before going to production.
P.76SQLite runs in every phone and browser. Turso extends it to the server and edge with replication, branching, and a network protocol. Here's when it makes sense.
P.77Command-line tools are underrated as developer products. TypeScript makes them maintainable. Here's the full picture: argument parsing, interactive prompts, output formatting, and distribution.
P.78The Date object has been broken for 30 years. Temporal is its replacement, now shipping in browsers and Node.js. Here's what actually changed and how to use it.
P.79Most slow queries come from a small set of fixable problems: missing indexes, N+1 patterns, and over-fetching. This is the practical diagnostic and fix guide.
P.80Blue-green and canary deployments give you a way to release software without taking down your service or discovering a bug when it's already affecting everyone. Here's how they work and when to use each.
P.81NestJS has been growing quietly for years. If your Node.js backend is a pile of Express middleware with no clear structure, NestJS offers a path forward without changing languages.
P.82eBPF lets you attach programs to any kernel hook — network packets, system calls, function calls — without patching the kernel or rebooting. Here's what application developers actually need to know.
P.83Clients ask agencies to 'do something with these PDFs' more often than you'd think. Here's how to actually build document extraction pipelines that work in production: OCR, vision models, and structured output.
P.84Local-first means your app works offline and syncs when connected. The technology (CRDTs and sync engines) is mature enough to use. The question is whether your use case actually needs it.
P.85DuckDB runs OLAP queries directly in your process, on files on your laptop, without a server. Here's how to use it and when it beats spinning up BigQuery or Redshift.
P.86Row Level Security moves data isolation into the database where it belongs. Here's how to set it up for a multi-tenant SaaS, handle common edge cases, and avoid the traps that break it.
P.87Go has real strengths for backend API work, and some persistent limitations. Here's what teams actually gain and give up when they choose it over Node.js or Python for web APIs.
P.88A hands-on comparison of Typesense, Meilisearch, and Algolia for production SaaS search in 2026 — covering self-hosting, performance, pricing, and real implementation patterns.
P.89A practical guide to building SaaS billing with Stripe in 2026 — covering subscription plans, the Meter API for usage-based pricing, webhook reliability, and the Customer Portal.
P.90A practical guide to transactional email for web apps in 2026 — comparing Resend, Amazon SES, and SendGrid, with a focus on SPF/DKIM/DMARC setup and the common deliverability mistakes teams make.
P.91How Zod became the standard for runtime type validation in TypeScript apps — API contracts, form validation, environment variables, and the patterns that make schemas a source of truth across your stack.
P.92Both approaches customize LLM behavior for your use case, but they solve different problems. Here is how to decide which one you need, how to know when to use both, and what teams consistently get wrong.
P.93OpenTelemetry is the observability standard now. Most tutorials show you how to install the SDK and emit traces. Fewer explain which signals actually matter for web applications and which add noise without helping you debug anything.
P.94Password resets, invoices, and notification emails are infrastructure. Most developers treat them as an afterthought until a client asks why their welcome emails are disappearing. Here is the full picture.
P.95Stripe's API surface has grown well beyond checkout forms. Here's the realistic breakdown of which Stripe products matter for agency work, which are overkill, and where teams consistently get burned.
P.96An agent that forgets everything when the session ends is a limited tool. Here are the practical patterns for building different kinds of memory into your agents.
P.97When your AI agent needs to run the code it writes, you can't let it touch your production servers. Here's how the main isolation options work and when to use each.
P.98HPA scales on CPU and memory. But most production workloads don't scale well on those signals. KEDA, VPA, and Goldilocks fill the gaps that HPA leaves open.
P.99The implicit flow is dead, and most tutorials still teach it. Here is how authorization code flow with PKCE actually works, how tokens should be stored, and where most SPA auth implementations go wrong.
P.100Bad documentation is usually not a writing problem — it's a maintenance problem. AI tools are changing the equation by making initial doc generation cheap and doc refresh practical at scale.
P.101The queries that destroy production Postgres databases share a small set of root causes. Here is how to find them, understand what EXPLAIN ANALYZE is telling you, and fix them without guessing.
P.102JavaScript error handling is broken by default — exceptions are untyped, async errors are easy to miss, and side effects are invisible in function signatures. Effect TS fixes all three. Here is how it works.
P.103Hono started as a tiny router for Cloudflare Workers and grew into the default choice for edge APIs. Here is what it does well, where it fits, and why the 'runs everywhere' claim is actually true.
P.104Single-provider AI dependencies are a reliability risk. Routing layers like LiteLLM and OpenRouter let you fall back across providers, cap costs, and try smaller models first. Here is the architecture and when it actually matters.
P.105Neon separates storage from compute to make Postgres behave like a serverless resource. The branching feature is what actually changes the development workflow — here's how it works and when it's worth the migration.
P.106gRPC has been available for years but many teams default to REST without thinking through the tradeoffs. Here's how gRPC works, where it fits, and where it doesn't.
P.107Python 3.13 shipped an experimental mode that removes the Global Interpreter Lock. Here's what the GIL actually does, what free-threaded Python changes, and what it still doesn't fix.
P.108Connection exhaustion is one of the most common production failures for apps that scale. Here's how pooling works, which tool fits which setup, and the configuration decisions that matter.
P.109Add similarity search to your existing Postgres database using pgvector. Real setup, indexing strategies, and when you actually need a dedicated vector database.
P.110Python 3.14 shipped in October 2025. Seven months in, the features worth caring about have become clear. Here's what changed, what to upgrade for, and what to ignore.
P.111From .env files to Vault to AWS Secrets Manager: a practical guide to storing credentials, API keys, and certificates without waking up to a breach notification.
P.112HTTP caching is one of the highest-leverage performance optimizations available, and one of the most consistently misunderstood. Here is how it actually works, why stale content happens, and how to design a caching strategy that does not surprise you in production.
P.113Breaking API changes are inevitable. How you handle versioning determines whether clients trust your platform or avoid integrating with it. Here's a practical comparison of URL versioning, header versioning, and content negotiation.
P.114Message queues and event streams solve different problems. Kafka is not always the right answer. Here's how to think through event-driven patterns and choose the right tool for your production workload.
P.115Every SaaS team eventually faces the multi-tenancy decision. The wrong choice creates migration pain later. Here's how to think through database-per-tenant, schema-per-tenant, and row-level security based on what your product actually needs.
P.116Running totals, rankings, moving averages, lag and lead comparisons: window functions handle the analytics queries that would otherwise require application-side loops or multiple round-trips. Here's how they work.
P.117Drizzle ORM has become the go-to choice for TypeScript projects that want type safety without the overhead of a heavy ORM. Here's how it works, how to migrate from Prisma, and when to use it.
P.118Code-first API development produces documentation as an afterthought. OpenAPI-first flips that: you write the spec, generate the server stubs and client SDKs, and enforce the contract at every layer. Here's how it works in practice.
P.119Not every real-time feature needs WebSockets. Server-Sent Events handle most push scenarios with far less complexity. Here's how to choose, and what each approach looks like in actual code.
P.120Background jobs that crash mid-execution lose all their state. Temporal solves this by making workflows durable state machines that survive process restarts, deploys, and outages. Here's what it looks like in TypeScript and Python.
P.121Every public API needs rate limiting, but the algorithm you choose shapes the user experience and the failure modes. Here's how each approach works and when to use it.
P.122In March 2024, Redis Ltd. relicensed Redis under a source-available license. Within weeks, the Linux Foundation forked it as Valkey. Two years on, here's how the split played out and what it means for teams choosing an in-memory data store today.
P.123LLM calls are slow and expensive. Caching them is the obvious move. But caching the wrong responses breaks the user experience in ways that are subtle and hard to debug. Here's a practical guide to doing it right.
P.124Getting a language model to return valid, schema-conforming JSON is harder than it looks. Here's what works in production, from native structured output APIs to library-level validation.
P.125ALTER TABLE locks your database. Your migration takes longer than expected. Users get errors. Here's how to handle schema changes that don't interrupt production traffic.
P.126Async Django is production-ready in 2026, but landmines still exist. Four real projects, benchmarks, and a framework for deciding when async actually helps.
P.127EditorPickWe migrated three production projects from Celery to Django's new Tasks framework. Two went smoothly. One was a disaster. Here is everything we learned.
P.128EditorPickThe network latency between your Django app and your FastAPI ML service is probably longer than inference itself. Here is how to serve models from Django directly.
P.129EditorPickWe rebuilt a React SPA as a Django + HTMX app. 847KB of JavaScript became 48KB. Here is every pattern, rough edge, and performance win from the migration.
P.130EditorPickMost DRF vs FastAPI comparisons are written by people who only use one. We ship both in production. Here is what actually matters and when to choose each.
P.131The API landscape has matured beyond the GraphQL vs REST debate. Here's how to choose between REST, GraphQL, tRPC, and gRPC based on your actual requirements.
P.132WebAssembly is no longer just a browser technology. Server-side WASM, the component model, and WASI are reshaping how we build and deploy software across cloud, edge, and embedded systems.