Client-Side Event Sourcing: Beyond the Three-Tier Web

Local-First Data Revolution

Johannes Schickling's exploration of moving beyond the traditional three-tier web stack to a client-side event sourcing model, as detailed in this InfoQ podcast, presents a compelling vision for building more responsive and resilient applications. The core insight is the redefinition of 'Local-First' not just as offline support, but as a strategic shift of the data bottleneck from the server to the client. This has profound implications for user experience, enabling desktop-like performance and reliability directly within web applications. The discussion around event sourcing as a foundational technology for this paradigm is particularly noteworthy. Unlike CRDTs, which are often discussed in the context of real-time collaboration and conflict resolution, event sourcing offers a robust, immutable history of changes. This historical record is invaluable for debugging, auditing, and even for enabling complex features like undo/redo functionality or time-travel debugging, all while maintaining a local-first architecture. The practical application of this through Overtone, a music curation app, and the underlying LiveStore framework, demonstrates that these are not just theoretical concepts but are being actively developed and implemented. The emphasis on rigorous upfront planning for breaking down monolithic data structures is a crucial warning, highlighting that this architectural shift is not a trivial undertaking and requires careful consideration of the application's specific needs and user experience goals. The trade-offs between event sourcing and CRDTs are also well-articulated, guiding architects in making informed decisions based on their project's requirements.

Key Points

• Local-First architecture shifts the data bottleneck from the server to the client for enhanced performance and responsiveness.
• Event sourcing on the client-side offers a robust historical record of data changes, beneficial for debugging and complex features.
• The choice between event sourcing and CRDTs depends on application needs; event sourcing for history, CRDTs for collaborative conflict resolution.
• Transitioning to Local-First requires significant upfront planning, particularly in data structure decomposition.
• Not all applications are suited for Local-First; assess user experience benefits against architectural complexity.
• LiveStore is an open-source, SQLite-based, event-sourcing framework for building Local-First applications.

---

📖 Source: Podcast: Rethinking Data: Moving From the Traditional Three-Tier Web Stack to Client-Side Event Sourcing