u/krisajenkins

As a fun side project, I built wikiwatch.io, which shows a leaderboard of the Wikipedia pages being most actively edited right now. The architecture's pretty simple, and this video breaks it down. It's all just functions, tables and subscriptions.

(And schedules, which are really just functions triggered by tables. 😁)

In response to Tyler's recent scaling post, a few people have asked if you actually need that much performance. It's a fair question - most projects will only ever need a fraction of those 300,000 transactions per second.
So I wrote something explaining why that kind of scale is extremely valuable, even for smaller projects. It's all about speed, stress and money.