Architecture

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 Introduction The Challenge Why a Collection Endpoint Matters Designing the API Breaking Down the UI Dependencies The Refactoring Journey Achievements and ROI What We Learned Future Considerations Introduction In software development, the most impactful changes often aren’t about adding new features—they’re about rethinking how components interact. This iteration was one of those transformative moments where we fundamentally changed how our web UI communicates with our padel scoring system. ...

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 Introduction The Challenge: Mixed Responsibilities Phase 0: Architectural Cleanup Phase 1: Static Imports and Consolidation Building the Projections Layer Achievements and ROI What’s Next Introduction Over the past few weeks, Caroline (our AI assistant) and I have been working on a significant architectural improvement to the Scores project - implementing a Dynamic Query Registry with proper separation between transactional and analytical concerns. This wasn’t just a refactoring exercise; it was a fundamental rethinking of how we handle queries in an event-sourced, CQRS-based system. ...

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. ...

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 Architecture Evolution Understanding the Repository Pattern Aggregate Design Single Transaction Strategy Implementation Journey Benefits Realized The Architecture Evolution When Caroline, Claude, and I first built the event sourcing system for Scores, we followed a pattern we’d seen in many examples: separate command handlers, an intermediate evolver service, and projections consuming events. It worked, but as we added more features, we realized we’d created unnecessary complexity. ...