PostHog moves its warehouse off DuckDB five months after rebuilding on it
PostHog cites complex customer queries and DuckLake catalog strain, and says it rebuilt around Trino and its own HogLake format.
By RuntimeWire Staff · Published
Primary source: Hacker News
Why it matters
The reset shows where a popular single-node engine stops being a managed warehouse: instance sizing, catalog commits and protocol compatibility become the product. PostHog is betting that a distributed Trino engine and a Postgres-backed catalog it controls can handle customer workloads without making users predict compute in advance.
PostHog, co-founded by James Hawkins and Tim Glaser, is moving its managed warehouse off DuckDB five months after rebuilding it on the engine, replacing the design with Trino and a new open table format called HogLake. Benjamin Knofe-Vider laid out the reversal in a PostHog post on November 2nd, saying PostHog spent the last three months re-architecting the warehouse without DuckDB.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.