The Serverless Migration Decision: Cold-Start and Vendor Lock-in
Before you move to FaaS: the real cost of cold-start latency, vendor lock-in risk, and the workloads where serverless actually pays off
sade.dev
sade.dev — I write about production lessons, architecture decisions, database, server and application patterns, and AI-assisted engineering. Notes on one side, small but useful developer tools on the other.
Production notes and short technical explainers.
Before you move to FaaS: the real cost of cold-start latency, vendor lock-in risk, and the workloads where serverless actually pays off
Separate API layers for mobile and web: the hidden cost of bending one API to fit every client, and when a BFF is actually warranted
Should a job run inside the HTTP request or go to a queue? The decision line, drawn through response time, fault tolerance, and consistency
Full architecture breakdowns.
Writing to the database but failing to put the event on the queue: closing dual-write with an outbox, suppressing the at-least-once repeats it creates, and encrypting the field.
Why GPU spend is invisible to cgroup and cAdvisor metrics, and how eBPF attributes GPU time and memory to teams for chargeback — with the honest limit at the CUDA boundary that DCGM has to cover.
Developer tools that run entirely in your browser.
Encode and decode text with Base64. Supports the URL-safe variant. Unicode-aware.
Format and minify JSON. Runs in your browser, your data never leaves it.
Decodes the header and payload of a JSON Web Token. Does not verify the signature
Cryptographically secure password generator with adjustable length and character classes. Runs in your browser.
Decision logs and opinion pieces.
An architecture decision written in a wiki is a wish. The boundaries you can't enforce are the ones that quietly erode — until the diagram stops matching the code. Make the rule executable
Cheap code production doesn't raise throughput if review, integration, and verification can't keep up. The bottleneck just moves downstream — and that's where the work now is
The tools and server setup I use in production.