“Ducklake DuckDB extension” really rolls off the tongue /s.

IME, I've found sampling simpler to reason about, and with the sampling rate part of the message, deriving metrics from logs works pretty well.

The example in the article is a little contrived. Healthchecks often originate from multiple hosts and/or logs contain the remote address+port, leading to each log message being effectively unique. So sure, one could parse the remote address into remote_address=192.168.12.23 remote_port=64780 and then decide to drop the port in the aggregation, but is it worth the squeeze?

An approachable paper on the topic is "Effective Computation of Biased Quantiles over Data Streams" http://dimacs.rutgers.edu/%7Egraham/pubs/papers/bquant-icde....

…otherwise you can try Render, Fly.io, Google Cloud Run, Railway, etc.

The "about" link at the bottom of the home page links to https://hot.page/manifesto which is 404 Not Found.

A Docker registry backed by Workers and R2.

https://github.com/cloudflare/serverless-registry

The worst thing about PHP: shared nothing architecture.

It works extremely well until it doesn’t really scale anymore.