Integration
I measured the two halves of the claim separately — binary serialisation against JSON, and HTTP/2 against HTTP/1.1. Binary decoding is about twice as fast, which is worth 0.03% of a request. The transport is where the real difference lives.
Integration
One idle transaction that had read a single row made a Postgres 16 table grow 4x in five minutes under an ordinary write load. It blocked no queries and cost 0.2% of throughput — the damage was disk, and plain VACUUM did not give it back.
Integration
408, 425, 429, 500, 502, 503 and 504 are worth retrying; 400, 401, 403, 404 and 422 never are. The hard part is the network errors and the POSTs — a timeout on a POST means the request may already have succeeded.
Integration
We benchmarked a SKIP LOCKED job queue on Postgres 16 at 1 to 100 concurrent workers. It peaks near 16,000 claims a second — and the first thing to break is autovacuum, not row locks.
Integration
Conditional requests turned 60 polls into one unit of quota, and a keyset cursor stopped the poller silently dropping records that shared a timestamp. The three bugs are all invisible — nothing errors, you just quietly lose rows.
Integration
Read Retry-After and wait, instead of retrying into a wall — a client that obeys sent 43 requests where a blind one sent 55,930, and both finished in the same three seconds. Then publish your own limit as a token bucket, per customer.
Integration
Most teams reach for a stream and need a queue. Cron loses the window it missed and runs itself twice; a queue fixes both in one clause; a stream is only worth it when several consumers need the same events, or you need to replay them.
Integration
Store every step's input, output and error as rows the customer is allowed to read. It is the difference between "it failed, please send a screenshot" and the customer finding the 422 themselves.
Integration
Storing UTC is necessary and not sufficient. A daily 09:00 reminder computed by adding 24 hours drifts to 08:00 the day the clocks change — here is that bug, measured, and the four others around it.
Integration
new Function gives the user your permissions. Node's vm module looks like a sandbox and escapes in one line. The safe option is a grammar small enough that there is no path to the host at all.
Integration
The canvas is the easy part. What decides whether the product survives is storing flows as a versioned graph, keeping runs separate from definitions, and pinning each run to the version it started with.
Integration
You can have at-most-once or at-least-once. Exactly-once delivery is not available over a network that can drop packets — but at-least-once plus an idempotent handler gets you the thing people actually mean.