Leaderboard & Counting Service · View 05 of 21 · People and journeys
The finding
- The trough is a cost-and-accuracy decision the engineer is not equipped to make blind: exact or approximate, and what error is acceptable. Showing the unit cost of each counter type inside the definition turns a guess into a choice.
- A window-set change is the other hazard. It silently reinterprets events already counted, so the platform refuses it and creates a new counter version instead.
- A disposable sandbox tenant is what makes "try it" a real step rather than a staging ritual.
What the platform owes here
- A new counter or leaderboard live by configuration within one working day, with no platform code change.
- Configuration effective at ingestion within 60 s (assumption).
- A stated unit cost per million events for each counter type, visible in the change.
Risks
- Self-service plus per-tenant quotas means a team can declare a leaderboard whose read pattern is affordable in test and not in production. The ceiling has to bite before the bill does.
- Versioned counters accumulate. Without a retirement path the definition store becomes an archaeology site.
