← All stories
● Covered by 1 source · 1 reportLow impact1 neutral

Johannes Schickling Discusses Transition to Client-Side Event Sourcing and Local-First Development

🔄 Updated 1d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Local-First shifts data bottlenecks from server to client for performance.
  • Event sourcing offers robust history; CRDTs excel in conflict resolution.
  • Transitioning to Local-First requires careful planning for data structures.
  • Not all applications benefit from Local-First due to architectural complexity.

Rethinking Data Architectures

Johannes Schickling, known for founding Prisma, has explored moving beyond the conventional three-tier web stack. His current focus is on a local-first development approach, which he implemented in his music curation application, Overtone. This shift involves leveraging client-side event sourcing and SQLite.

Local-First Development Principles

Local-First development aims to move the data bottleneck from the server to the client, enabling high-performance and responsive user experiences. This approach prioritizes offline support and user data ownership, contrasting with server-centric models. Schickling's work with Overtone exemplifies this architectural change.

Event Sourcing vs. CRDTs

The discussion covered the trade-offs between event sourcing and Conflict-free Replicated Data Types (CRDTs) in local-first contexts. Event sourcing provides a robust history of changes, while CRDTs are designed for collaborative conflict resolution. The choice between these depends on specific application requirements and the need for historical data versus real-time collaboration.

Implementation Challenges and Considerations

Adopting a local-first architecture requires significant upfront planning, particularly in breaking down monolithic data structures into smaller, manageable units. Not every application is suitable for this paradigm; developers must assess if the benefits, such as offline capability and data ownership, justify the increased architectural complexity. Modern frameworks like LiveStore offer solutions for data portability and security within local-first systems.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~7 min · 6 stories · Aug 15

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Johannes Schickling, founder of Prisma, discussed his shift from traditional three-tier web stacks to a local-first approach using client-side event sourcing and SQLite for his music curation app, Overtone. This transition highlights the architectural considerations and trade-offs involved in moving data bottlenecks from servers to clients for improved performance and responsiveness.