blog
Blog — page 22 of 39
Posts 505–528 of 928, newest first.
Sandboxing SBOM and Vulnerability Scans of Untrusted Artifacts
A security scanner that runs against artifacts it doesn't control is, itself, running untrusted input through a parser. Give the scanner the same isolation you'd want it to recommend for anyone else's code.
Ajay KumarThe Best Browserbase Alternatives in 2026
If you run headless Chrome at scale, the question is rarely 'which API is nicest' — it's who owns the isolation boundary, what an idle session costs, and whether logged-in state survives. Here is the 2026 field.
Ajay KumarThe Best FastAPI Hosting Platforms in 2026
FastAPI is trivial to write and surprisingly easy to deploy badly. Here's the 2026 field, plus the async, worker-count, and cold-start details that decide whether your API actually holds up.
Ajay KumarThe Best Fly.io Alternatives in 2026
People leave Fly.io for four reasons, and they lead to four different replacements. Here's the 2026 field mapped to the constraint that's actually forcing your hand.
Ajay KumarThe Best AWS Lambda Alternatives in 2026
Nobody leaves Lambda because of the price per invocation. They leave because of cold starts, the 15-minute ceiling, VPC latency, or because the function was never really stateless.
Ajay KumarThe Best Cron Job Platforms in 2026
Scheduled jobs are the least glamorous infrastructure you own and the most likely to fail silently. Here's how the 2026 options differ on the things that actually matter at 3am.
Ajay KumarThe Best GitHub Codespaces Alternatives in 2026
Cloud dev environments split into two jobs now: a place for humans to write code, and a place for agents to run it. Codespaces is good at the first and awkward at the second.
Ajay KumarThe Best Deno Deploy and Edge Function Alternatives in 2026
Edge runtimes are fast because they're constrained. When you hit the constraint — native modules, long jobs, a real database connection — you need a different shape of platform, not a different edge.
Ajay KumarHow to Deploy a Nuxt App Without Docker
Nuxt builds to a plain Node server. You don't need a container to run it — you need to get four things right: the output path, the port binding, runtime config, and which env vars exist at build time.
Ajay KumarHow to Run Cron Jobs Without Managing a Server
Getting a job to run at 2am is the easy part. Knowing it ran, making it safe to run twice, and finding out when it stops — that's the actual work.
Ajay KumarHow to Migrate from Heroku to MicroVM Hosting
Your Procfile becomes a start command, your config vars become env vars, your dynos become VMs. The app moves in an afternoon; the database is the part that needs a plan.
Ajay KumarBuild-time vs runtime environment variables
You set the environment variable. The dashboard shows it. The build still fails with 'undefined'. This is almost always the build-time versus runtime distinction, and frontend frameworks make it considerably more confusing than it needs to be.
Ajay KumarWhy your JavaScript build runs out of memory
It builds on your 32 GB laptop and dies on the build machine with an exit code 137 or a heap-out-of-memory stack trace. Here's what's actually consuming the memory and which fixes are real.
Ajay KumarSchema migrations that don't take the site down
During a blue-green deploy, the old version and the new version are both talking to the same database. Every schema change has to be compatible with code that hasn't been deployed yet and code that's about to be deleted.
Ajay KumarRunning background workers next to your web app
Every app eventually needs work that outlives a request. Where that worker runs — same process, same machine, separate deployment — decides how it fails, and most teams pick by accident.
Ajay KumarHosting apps that hold persistent connections
A WebSocket connection is a long-lived, stateful thing on a platform designed around short, stateless requests. Every part of the deploy lifecycle has to be reconsidered, starting with what happens when you ship.
Ajay KumarDeploying one service out of a monorepo
The repo has six apps and a dozen shared packages. You want to deploy one of them. Everything that makes a monorepo pleasant to develop in makes this step awkward, and the failures are all the same handful.
Ajay KumarDeploying a Go service without writing a Dockerfile
Go produces one self-contained binary with no runtime to install. Wrapping that in a multi-stage Dockerfile to copy it into a scratch image is a lot of YAML to solve a problem Go already solved.
Ajay KumarConnection pooling, and why you ran out of connections
Postgres gives every connection its own operating system process. That single design decision explains connection limits, why pooling exists, and why serverless functions are so good at exhausting a database.
Ajay KumarWiring an app to managed Postgres with Prisma or Drizzle
Creating the database is the easy part. Getting an ORM connected, migrations running in the right place, and TLS verified is where the afternoon goes — so here is the whole path, in order.
Ajay KumarHow much memory does your Postgres actually need?
The advice 'give Postgres as much RAM as your data' is expensive and usually wrong. What matters is the working set — and there's a query that tells you whether yours fits.
Ajay KumarBackups you haven't restored aren't backups
Every team has backups. Far fewer can tell you how much data a failure would lose or how long a restore takes, and those two numbers are the only part of a backup strategy that matters.
Ajay KumarThe Postgres metrics worth watching
A default database dashboard shows CPU, memory and disk — three metrics that tell you almost nothing until it's too late. Here's what actually predicts a Postgres incident.
Ajay KumarTestcontainers, and what comes after it
Testcontainers solved a genuine problem: tests against a real Postgres instead of a mock. The limits show up later, when the suite gets parallel and the CI runner is itself a container.
Ajay Kumar