Learn
Architecture
How sparQ is built. Data models, system design, real-time infrastructure.
How sparQ handles real-time team status
Server-sent events, presence tracking, and the trade-offs we made to keep p99 under 200ms.
The blocker data model
Why blockers reference both tasks and people, how escalation paths are computed, and the migration that almost broke us.
Why server-sent events, not WebSockets
The boring tech choice that's outperformed our expectations. Operational notes from a year in production.