Performance

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Query Complexity Problem Three-Tier Improvement Strategy Tier 1: Zero-Risk Quick Wins Tier 1.5: Match Timing Lookup Table Tier 2: Shot Sequence Linking Tier 3: Score Denormalization Performance Impact Key Learnings The Query Complexity Problem When Caroline and I first built the ClickHouse analytics for Scores, we followed a pure event sourcing approach: store raw events, derive everything in queries. This kept writes simple but made reads complex. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Image Size Problem Multi-Stage Build Strategy esbuild Bundling Production vs Development Results and Lessons The Image Size Problem When Caroline and I first containerized the Scores services, we took the straightforward approach: install dependencies, copy the workspace, and run with tsx for TypeScript execution. Simple, but expensive. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Connection Problem Singleton Connection Managers Channel-Based Message Routing StreamConnection Implementation EventConnection Implementation Component Integration Server-Side Changes Results and Benefits Key Learnings The Connection Problem When Caroline and I were building the recorder page for Scores, we noticed something alarming: each web component was creating its own connection to the server. The audio recorder had a WebSocket, the manual input component had another WebSocket, each of the four biometric monitors had their own WebSocket, and the score dashboard, match highlights, and real-time updates each had EventSource connections. ...