How many clicks per second on an item would justify this architecture? Ballpark numbers and napkin math estimates is fine - again it would seem reasonable if justified.

If I’m gonna get that many clicks per second, it’s likely I’ll already have my own analytics system, queue system, cache architecture, application database. Why adopt this external code when I’ll spend more work integrating it into my application compared to building it myself?

If I’m small, why spend all the work or subscribe to your managed product when a very simple CRUD approach using only my app database and polling will suffice?

Anyways that’s my perspective. There’s probably some market out there but I’m not part of it, that’s all I’m saying.