blog

Blog — page 24 of 39

Posts 553–576 of 928, newest first.

9 min read

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.

securityrubysandboxAjay Kumar
9 min read

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.

firecrackermicrovmapiAjay Kumar
9 min read

Snapshot-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.

firecrackersnapshot-restorelive-migrationAjay Kumar
8 min read

Deploying 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.

app-hostingnextjsdeploysAjay Kumar
8 min read

Scale-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.

app-hostingscale-to-zerocostAjay Kumar
9 min read

What 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.

paasfirecrackerarchitectureAjay Kumar
8 min read

How 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.

deploysgithubwebhooksAjay Kumar
9 min read

PandaStack 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.

comparisonrenderapp-hostingAjay Kumar
9 min read

PandaStack 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.

comparisonrailwayapp-hostingAjay Kumar
9 min read

The 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.

herokupaasapp-hostingAjay Kumar
8 min read

Custom 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.

custom-domainstlsapp-hostingAjay Kumar
8 min read

Deploying 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.

pythonfastapiapp-hostingAjay Kumar
9 min read

Running 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.

databasespostgresmicrovmAjay Kumar
8 min read

Postgres 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.

postgresdatabasesbackupsAjay Kumar
8 min read

Cloning 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.

databasestestingpostgresAjay Kumar
8 min read

Suspending 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.

databasespostgresscale-to-zeroAjay Kumar
7 min read

Routing 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.

postgresnetworkingtlsAjay Kumar
8 min read

Database 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.

databasespostgresreliabilityAjay Kumar
7 min read

Rotating 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.

postgresdatabasessecurityAjay Kumar
8 min read

End-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.

testinge2edatabasesAjay Kumar
8 min read

A 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.

stagingpreview-environmentsdatabasesAjay Kumar
8 min read

Contract 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.

testingmicroservicesciAjay Kumar
8 min read

Why 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.

testingbrowser-automationvisual-regressionAjay Kumar
9 min read

Running 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.

reinforcement-learningmicrovmsandboxAjay Kumar