Integration
We fed 48 timestamp shapes from real APIs to new Date() under three server timezones. It returned the wrong instant for 4, 6 or 9 of them depending only on TZ, and Invalid Date for 11 more. date-fns and luxon disagree with it on date-only strings.
Integration
Yes, by about 3x on HTTPS. At 380 ms RTT, a reused connection answered in 385 ms against 1,153 ms for a new one, measured with server-side connection counts. The catch is a stale-socket race that cost 14 to 19 errors per 1,000 requests until we fixed the idle timeout.
Integration
We applied 12 realistic breaking changes to a live API and measured which detection method caught each. Runtime validation caught 7 of 12, a recorded golden response 9, property checks 9, TypeScript 0. Validating every response costs about 20 microseconds.
Integration
You send it all again. A 256 MiB single POST killed at 90% wasted 242,221,056 bytes and needed 510,656,512 bytes in total to succeed; the chunked version re-sent 419,430 bytes — 577x less. Measured on Node 23: chunk size against failure rate, resume discovery, per-chunk checksums, parallel chunks, t
Integration
max-age — and it is the only one on the list that saves a round trip. Measured on Node 23: a 304 from an ETag saved 307,502 of 307,835 bytes on a 300 KB bundle but still took 53.7 ms on an emulated 50 ms link, against 0.00 ms for a max-age hit. Includes the ETag hashing cost (md5 is 4.5x slower than
Integration
LIMIT/OFFSET is only correct if the table stops changing while you read it. Paging 100,000 rows on Postgres 16 while 100 a second were deleted lost 1,092 rows and raised no error. Keyset lost none — and the tiebreak on id is not optional.
Integration
Accepting an Idempotency-Key header is the easy part. The SELECT-then-INSERT check almost everyone writes lets 969 duplicate charges through 1,000 concurrent requests. Here is what actually holds, measured on Postgres 16.
Integration
You stream it — and on Node 23 you have no choice, because fs.readFile refuses any file of 2,147,483,648 bytes or more with ERR_FS_FILE_TOO_LARGE. Below that ceiling the buffered version works fine on your laptop and dies under load: five concurrent 1 GB downloads cost 5,166 MB of RAM buffered again
Integration
Node 23's fetch waits 301 seconds for a response and http.request waits forever — measured. Long before that, a slow vendor took a healthy database endpoint from 100% to 7.7% success, while the endpoint that touched nothing stayed at 100%.
Integration
Of eighteen DDL statements measured on a 10-million-row Postgres 16.15 table, three rewrote it and froze every read and write for about 8 seconds. The other fifteen finished in under a second — and one of the cheap ones still stopped reads for 18 seconds.
Integration
Measured on Postgres 16 with a 497 MB, 5,000,000-row CSV. COPY FROM STDIN ran at 1,265,000 rows a second - 120x a loop of single-row INSERTs - and six parallel connections reached 3,571,000. The multipliers everyone repeats are not equal: dropping indexes was worth 2.3x, UNLOGGED only 1.2x, and sync
Integration
Five steps in order — fail readiness, wait for the load balancer, stop accepting, drain in-flight work, force-exit on a deadline — and a grace period longer than your slowest job. Measured on Node 23 and Docker 29.