clickhouse
for data engineers, backend teams
Why this scored 10
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 123
How We Built a Data Warehouse Using ClickHouse
Step-by-step guide to building a data warehouse on ClickHouse for analytics workloads. · for data engineers, backend teams
lobstersEmergingdata38d ago - 217
Deploying SigNoz in 2026: A Survival Guide to ClickHouse v25+ and OTel Gotchas
Deploying SigNoz with ClickHouse 25+ and OTel requires careful architecture to avoid observability pitfalls. · for SREs, observability engineers
devtoSteadydevtools67d ago - 315
Clickhouse is winning the Observability Wars
Clickhouse observability
lobstersSteadydata113d ago - 410
@clickhouse/rowbinary: when your library is also a parser compiler
Row binary parser · for data engineers
lobstersSteadydata103d ago - 57
Andy Pavlo joins ClickHouse to establish ClickHouse Labs
new lab established · for data founders
hackernewsSteadydata83d ago