Thanks to @davidism and the people behind the scenes, my talk "Death to the spinner: event sourcing for reactive web apps" is now available.
It shows how to create a reactive web experience with #eventSourcing and the #dataStar JS framework.
https://www.youtube.com/watch?v=H3jNUpT1Ok4&list=PL-MSuSC-Kjb5QUUucArxREc8Ix3S1cPsk&index=5
We released 1.1.0 of laravel-event-sourcing! See here for the changelog: https://github.com/patchlevel/laravel-event-sourcing/releases/tag/1.1.0
#PHP #DDD #EventSourcing #Laravel
You wouldn't hate stored procedures so much if you didn't have to maintain and author sql code. The behaviour-data separation is a dysfunction that was born decades ago and persists today. Break free from this & other dysfunctions in one step by #EventSourcing & #EventModeling.
We need reference material for #EventSourcing and #DynamicConsistencyBoundary that doesn't use a database. Databases are overkill for ES solutions as the functionality you need out of a Db for any projection (CH or RM) is very focused in scope and hence easily implemented from the ground up for locking and indexing. The future doesn't look good for RDBMS in ES solutions.
Added a simple API to reset an entire #eventsourcing consumer group in #ruby and start re-building projections from events, from scratch. This was possible before, but it's nice (and dangerous!) to have a little button for it.
On my way to SDD 2025 in London today. Meet me there for one of my presentations on #CSharp, #EventSourcing, #Docker, #FunctionalProgramming, or my C# Masterclass. Say hello if you’re there! #sdd2025 https://sddconf.com
On Friday at 5:15, I'll be speaking about how #eventSourcing can make your app faster at #FlaskCon!
I’ll be speaking about #ruby and #eventsourcing at LRUG tonight. Come say hi and maybe have a 🍺 afterwards!
Peter Royal will go over the design and implementation of an application that is helping power Netflix’s studio. Borrowing ideas from #EventSourcing and #CQRS, he will show how this model is aligned with modern cloud-based architectures and capabilities desired in business applications. https://youtu.be/Hg9JYyciJvk
"One of the most interesting things about #EventSourcing is its natural alignment with human thinking" - ch.2, p.9
That's a bold statement and it needs proofs or strong arguments at least. The OOP evangelists used to say that objects were naturally aligned with human thinking. And BORO claims that entities and their attributes are a good approximation of how people see the world.
So, who's right then?
Isn't this claim just a marketing slogan?
"#EventSourcing as an implementation pattern is rather simple. Instead of storing your data in tables and relations, you store the facts that actually happened in the system in the order they happened." - ch.1, p.3
So, events (or facts) are the stored representation of things that really happened inside the system.
That's important, I think, because it means that we're not modeling the real world, we're logging what happened in our software system.
On my #Java live coding stream, I'm building an example app that uses #EventSourcing, and just finished a simple "time-traveling" event viewer. The aggregate viewed here has a bunch of events (scheduled, rescheduled, ticket sales) and we're looking at state as of the 2nd event:
Traceability, Consistency, Correctness. Why Nordic fintech Lunar chose #eventsourcing and the challenges it brought. https://youtu.be/lhwBmE_3X_c
I'm working on something, but it is not public yet. More info soon. #php #eventSourcing
I'll be speaking at #FlaskCon with a talk I'm excited to present:
Death to the spinner—event sourcing for reactive web apps.
It'll be a practical follow-up to my blog series, making the last entry a little late.
See you there!
🚨Join us on Wednesday 21st of May for our event on Feedback Loops & Event Sourcing 🚨
_Event-Sourcing Live Coding_
I've been live coding an example #EventSourcing app in #Java (via #TDD) w/o an ES library.
This week I'll continue to code the "Time-Traveling Event Viewer" to view the state at any point in time.
Join me Mon-Thur 18:00 UTC https://jitterted.stream
I'll be talking about my #eventsourcing #ruby shenanigans @lrug this 12th of May https://lrug.org
The week is coming to a close, and I'm meeting my internal goal to publish the fourth of five blog posts about my experience with event sourcing, vertical slice architecture, and event modeling. Enjoy it!
Part 4: Event Sourcing: Reactivity Without the React Overhead
https://everydaysuperpowers.dev/articles/event-sourcing-reactivity-without-the-react-overhead/
Past week I had the opportunity to write about the difference between Domain Events and Change Data Capture patterns.
Nowadays I'm very much involved in the implementation of these patterns and I wanted to share my learnings on that.
As Senior Software Engineers and Tech Leads we have to learn common patterns to solve problems in the most simple way and avoiding “reinvent the wheel”.
I want to thank Raul Junco for giving me the space on his newsletter and reaching his audience for this.
You can read it here 👇🏼
#softwareengineering #leadership #eventsourcing #eventdriven
