iampims

I’ve started pair programming with Claude and it’s been pretty fun. We make a plan together, I type the code and Claude reviews it. Then we switch.

You should write something about this…

Great idea, poor naming. If you’re aiming for a standard of sorts, tying it to a specific software by reusing its name feels counter productive.

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

but that'd be real money, not the Monopoly money they used to buy Ive/Windsurf...

Not sure I would qualify sharding a DB that get 1M qps as straight forward. I agree with you that it seems that an org would be a natural sharding key, but we know that at this scale, nothing really is ever straight forward, especially when it's your first rodeo.

I just wish Meta would open source Scuba.

lossy and simpler.

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?

Or sampling :)

Some serious engineering here. Kudos!

It'll work. Clickhouse has even experimental support for storing prometheus metrics natively. A big missing piece is alerting.

Heroku is still around…

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

If the LB is for HTTP traffic, check out Cloudflare’s offering.