blog
Blog — page 24 of 39
Posts 553–576 of 928, newest first.
Running bundle install on untrusted Ruby code in a microVM
bundle install doesn't just run scripts — for gems like nokogiri, pg, and bcrypt it invites a C compiler to build attacker-controlled source on your machine. Here's how to make that safe.
Firecracker config file vs REST API: two ways to boot a microVM
Firecracker will take your machine description two different ways: hand it one JSON document up front and let it boot itself, or drive it step by step over a socket. They produce the same VM. They are not interchangeable.
Ajay KumarSnapshot-Restore vs Live Migration: Not the Same Problem
Live migration moves ONE running VM to a new host without dropping it. Snapshot-restore freezes ONE VM once and restores it as MANY new ones. They both involve freezing a machine and picking it up somewhere else, and that's exactly where the confusion starts.
Ajay KumarDeploying a Next.js app to a microVM from git
Git-push deploys are a solved problem right up until the build machine and the runtime machine are the same box, or the runtime is a container that quietly shares a kernel with forty strangers. Here's the pipeline when every app gets its own VM instead.
Ajay KumarScale-to-zero app hosting, and what it costs you
Most hosted apps serve nothing for most of the day, and you pay for all of it. Scale-to-zero fixes that — as long as you understand the wake path, and as long as your uptime monitor isn't quietly defeating the whole thing.
Ajay KumarWhat it takes to build a PaaS on Firecracker
Every few months someone posts 'I built a Heroku in a weekend on Firecracker'. The VM part is genuinely a weekend. The other nine components are where the next two years go — here's the honest inventory.
Ajay KumarHow push-to-deploy works under the hood
Push-to-deploy looks like magic and is actually five unglamorous mechanisms in a trench coat. Knowing which one is broken saves you from re-pushing an empty commit and hoping.
Ajay KumarPandaStack vs Render: an honest comparison
Both take a repo and give you a URL. The difference is what your code lands in — a container sharing a host kernel, or a microVM with its own — and that decides isolation, what you can install, and how idle apps bill.
Ajay KumarPandaStack vs Railway: an honest comparison
Railway has some of the best developer experience in hosting. The question isn't whether it's good — it is — but whether a container is the right box for what you're running.
Ajay KumarThe best Heroku alternatives in 2026
Everyone's migration post lists the same eight platforms. The harder question is what Heroku was quietly doing for you that the shortlist doesn't, and which of those things you'll have to rebuild.
Ajay KumarCustom domains and automatic TLS, done properly
Letting customers point their own domain at your app is four days of work and one very bad security bug. Here's the ordering that avoids the bug, and why wildcard certs cover less than you think.
Ajay KumarDeploying FastAPI without writing a Dockerfile
Python deploys fail in four predictable places, and three of them have nothing to do with your code. Here's each one, why it happens, and the fix — no container image required.
Ajay KumarRunning managed Postgres inside a microVM
Container-per-database and VM-per-database look similar on a diagram and behave nothing alike under load. Here's the architecture, why creates take 30 to 90 seconds, and what a VM buys a database that a container can't.
Ajay KumarPostgres point-in-time recovery, explained
A nightly dump gives you a bad day. PITR gives you the minute before someone ran the wrong UPDATE. The mechanism is simpler than it sounds, and the operational details are where it fails.
Ajay KumarCloning production data for testing, safely
Your seed script creates 50 tidy rows. Production has 40 million messy ones, three encodings, and a customer whose name breaks your CSV export. Testing against a clone finds those — if you handle the data properly.
Ajay KumarSuspending idle Postgres databases
A per-customer database fleet is mostly asleep and entirely billed. Suspending idle databases fixes that — but a connection arriving at a suspended database has to be held, not refused, and that's where implementations differ.
Ajay KumarRouting Postgres connections by SNI
Postgres has no Host header. So how does one endpoint on port 5432 route to a thousand different databases? The answer is in the TLS handshake, and it involves a protocol quirk unique to Postgres.
Ajay KumarDatabase failover when the host disappears
Failover is the operation most likely to turn a degraded database into a lost one. The mechanism matters less than one rule: never take down something healthy while trying to fix something you think is broken.
Ajay KumarRotating database credentials without downtime
Everyone agrees credentials should be rotated. Almost nobody does it, because the naive version drops every connection in the fleet. Here's the version that doesn't.
Ajay KumarEnd-to-end tests with a real app and a real database
The bugs that reach production are the ones between components — the transaction that isn't, the migration that locks, the constraint your mock didn't have. Testing those needs real things, one set per run.
Ajay KumarA staging environment per branch, database included
Preview URLs are standard now. Preview databases mostly aren't, so every branch still points at the one shared staging database — which is why your migrations still break each other.
Ajay KumarContract testing when you can run the real services
Pact and its relatives were designed around a constraint: you can't run twelve services in CI. That constraint has weakened. What survives is the part about who owns the expectation.
Ajay KumarWhy your visual regression tests are flaky
A visual regression suite that cries wolf gets muted within a month. Almost every false positive traces to the rendering environment, not the code — and that's fixable.
Ajay KumarRunning RL environments in microVMs: isolating rollout workers
An RL environment is the only workload where something is actively optimizing to break it — because breaking it pays. That changes what "sandbox" has to mean.
Ajay Kumar