The latest articles on DEV Community by Scott Bellware (@sbellware). https://dev.to/sbellware https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F77736%2F67dbc75b-c8be-4cbd-ac51-130052e45b26.jpeg https://dev.to/sbellware en Scott Bellware Thu, 07 May 2026 17:47:45 +0000 https://dev.to/sbellware/the-next-generation-of-eventide-2ica https://dev.to/sbellware/the-next-generation-of-eventide-2ica <p>After more than ten years of real-world development, production systems, and training 200+ engineers in event-sourced architecture, the Eventide project is entering its next phase.</p> <p>This article covers what's changing, what isn't, and why the accumulated experience of a decade makes now the right time to evolve the framework.</p> <p>Key points:</p> <ul> <li>The core architecture (event messages, command messages, entities, projections, components) isn't changing</li> <li>Developer experience is getting a significant improvement — Eventide is becoming more framework and less toolkit</li> <li>Common messaging patterns that teams kept building themselves will become first-class features</li> <li>Message DB is gaining independence and broader applicability beyond Eventide</li> <li>Contribution opportunities are expanding, including AI-assisted tooling for contributors</li> </ul> <p>Full article on the Eventide blog:<br> 🔗 <a href="https://blog.eventide-project.org/articles/the-next-generation-of-eventide/" rel="noopener noreferrer">https://blog.eventide-project.org/articles/the-next-generation-of-eventide/</a></p> eventsourcing architecture ruby opensource