Tag
57 articles tagged #Infrastructure.
P.01Cron jobs fail in three specific ways in production: overlapping runs, missed runs after downtime, and silent failures nobody notices. Here's how to close all three.
P.02vLLM v0.28.0 moved bitsandbytes quantization out-of-tree, breaking upgrades for 4-bit and 8-bit inference. How to check if you're affected and fix it fast.
P.03A single unauthenticated request can run code inside OmniRoute, the 58k-star AI gateway. Patch status is contested, so verify your build yourself.
P.04MikroTik patched three RouterOS bugs after CISA confirmed active exploitation of two: which CVEs to prioritize and how to check your router for compromise.
P.05Cloudflare logged 13 incidents between August 7 and 14, touching R2, Durable Objects, and Workers KV. What that means for building on one edge provider.
P.06Two writes hit different replicas at once. Which came first? Sometimes neither. How vector clocks tell a real conflict from a false one, without wall time.
P.07Amazon closes Mechanical Turk and Ground Truth's human workforce on September 30, 2026, after 21 years. The dates that matter, and where teams are moving.
P.08Argo Rollouts replaces a Deployment with a controller that shifts traffic gradually and rolls back on bad metrics. Real manifests, plain Deployment to canary.
P.09Every rolling deploy drops a few requests and the errors look like client noise. The shutdown sequence, the race behind it, and the code that fixes it.
P.10Kitesurf is a browser runtime with no UI or tabs, built for AI agents to load pages and extract HTML. It claims 3-7x less CPU than Chromium. When to use it.
P.11From Node.js 27 in October 2026, Node drops the odd/even model for one major a year, and every release becomes LTS. What changes, and how to plan for it.
P.12An SLA is a promise with a penalty. An SLO is the internal target that keeps you inside it. An error budget is what's left. The math, on a real example.
P.13BullMQ for Node, Celery for Python, Sidekiq for Ruby, and Temporal or a cloud queue when you need durability without owning a broker. The reasoning.
P.14CISA added CVE-2025-68686, a FortiOS SSL-VPN symlink persistence bypass, on July 27. It only bites devices compromised earlier and never forensically cleaned.
P.15Platform engineering has its own hiring cluster now, distinct from DevOps, SRE, and cloud architecture. How to screen for product thinking over ticket-taking.
P.16Deno 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.17GPT-5.6 Sol runs on Cerebras wafer-scale hardware at up to 750 tokens per second, roughly 10x typical GPU inference. Who that speed is actually for.
P.18DevSecOps is distinct from DevOps and from security engineering. What the role covers, what to screen for, and why supply chain security is now the core.
P.19SRE is a discipline, not DevOps with a pager. How to define the role, screen for reliability math, and avoid hiring an ops generalist by accident.
P.20Firebase's complexity and Supabase's Postgres assumptions don't fit every project. How PocketBase, Appwrite, and Convex differ, and when each one fits.
P.21Cloud architect is a badly misused title. How to define the role, screen for real judgment, and avoid hiring a certification collection by mistake.
P.22Data engineers build the pipelines, warehouses, and transformation layers. They aren't data scientists, backend developers, or analysts. How to hire for it.
P.23Go runs Kubernetes, Docker, Prometheus, and most cloud tooling. What the language attracts, what it demands, and how to screen for the right profile.
P.24Three tools, three bets on where complexity belongs. How to choose between BullMQ, Inngest, and Temporal based on what your system needs, not what sounds big.
P.25OpenFeature is a CNCF incubating project with broad SDK support. How to use vendor-neutral feature flags, and why the standard beats the tool behind it.
P.26Durable Objects solve edge computing's coordination problem: consistent state across distributed nodes. Here's how they work and when to use them.
P.27Kafka is the default for message queuing at scale. For teams under a million messages a day, NATS JetStream gives the same guarantees with far less overhead.
P.28Setting up metrics with Prometheus and dashboards with Grafana: what to instrument, what to skip, and what a dashboard should show during an incident.
P.29Dev Containers define your entire dev environment in a devcontainer.json file, so new teammates are productive in minutes. Here's how to set them up.
P.30Vulnerability scanning catches known CVEs in your base images before they reach production. Here's how to set up Trivy and Snyk, read their output, and act on findings.
P.31Multi-stage Docker builds cut image size by 80-90%, speeding up pulls, cold starts, and CI, while shrinking your attack surface and registry bill.
P.32R2'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.33Logs say what happened. Error tracking says what broke, for which users, in what context. Setting up Sentry properly, without the alert fatigue.
P.34Every cloud decision locks you in somewhere; the real question is which lock-in costs less. A practical framework for when to abstract and when to accept it.
P.35ClickHouse answers queries over billions of rows in seconds that take Postgres minutes. Here's how it works and what to know before adopting it.
P.36Blue-green and canary deployments limit the blast radius of a bad release. Here's how each works, with real Kubernetes and Argo Rollouts configs.
P.37eBPF attaches programs to any Linux kernel hook, network packets, syscalls, function calls, without patching the kernel. Here's what developers need to know.
P.38Tailscale is a mesh VPN giving distributed teams private networking between laptops, servers, and office machines in about 30 seconds, no VPN hardware needed.
P.39Multi-cloud usually costs more in engineering time than the lock-in risk it prevents; most teams do better on one cloud with deliberate exceptions.
P.40OpenTelemetry is the observability standard now, but most tutorials skip the hard part: which signals help you debug, and which just add noise and cost.
P.41Password resets and invoices are infrastructure. Here's how SPF, DKIM, DMARC, IP warmup, and bounce handling decide whether your email lands in the inbox or spam.
P.42When 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.43HPA 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.44The queries that wreck production Postgres share a few root causes. How to find them, read EXPLAIN ANALYZE properly, and fix them without guessing.
P.45LiteLLM and OpenRouter add failover, cost caps, and model fallback to your LLM calls. Here is how each works and when a routing layer is worth building.
P.46gRPC 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.47Connection exhaustion is a common production failure at scale. Here's how pooling actually works, which tool fits which setup, and the config decisions that matter.
P.48A practical incident response process for small teams: severity tiers, on-call rotations, better alerting, and blameless postmortems, no SRE org required.
P.49Leaked credentials are the most preventable breach category. When you need a real secrets manager, which one to pick, and what to do if you're still on .env.
P.50Most teams adopt a service mesh before they actually need one. Here's the decision framework, real cost tradeoffs, and when Istio, Linkerd, or Cilium earns its keep.
P.51Kafka isn't always the right call for event-driven systems. Choose between Kafka, Redis Streams, and BullMQ based on real throughput and durability needs.
P.52Background jobs that crash mid-run lose their state. Temporal makes workflows durable state machines that survive restarts and deploys. In TS and Python.
P.53HashiCorp's 2023 BSL relicensing split Terraform into OpenTofu, while Pulumi took a code-first approach. Here's how to choose between them in 2026.
P.54Valkey is the BSD-licensed Redis fork backed by AWS, Google, and the Linux Foundation. Here's how it diverged from Redis and when to migrate.
P.55Multicloud is worth it for data residency rules, acquisitions, or a workload one cloud does far better. For most teams, one cloud across regions costs less.
P.56GitOps adoption hit 64% in 2025, but costs rose with it. Real-time cost visibility in every infrastructure PR is how serious teams are fixing that in 2026.
P.57Astro powers our site, Vercel deploys it, Airtable runs our CRM, and Satori generates OG images. Here is every tool in our stack and why we picked each one.