Do you let the ORM persist your aggregates and record just the events for the aggregate root or do you let the ORM persist all entities seperately and record events for all data changes of all entities of you aggregate?
I just updated my #EventSourcing self-paced kit for .NET. You don't know what's that? I have a bit of a philanthropic rule: whatever code I do for my paid workshops, I'm open-sourcing it.
All backing exercises for my workshops are available for free, and you can try to do them on your own. They all have tests that will tell you if you made them well, plus some recommended solutions.
1/
🐍 At EuroPython 2024, our reviewers are at it going through more than 600 proposals!! If you know one, give 'em a cheer! And if you're a reviewer, keep going strong! 🚀 More reviews mean an awesome schedule! #ThanksReviewers 🙌🎉
@europython I went through 3/4th of the proposals so far. There are too many interesting proposals, even more so than previous years I find. What a nice predicament to experience!
Especially excited to see (relatively) many people wanting to share their stories and retrospectives (which has been historically lacking from soloists & small teams), #eventsourcing for all knowledge levels, and more nuances on #pythontyping (it's not a yes/no story for #python ).
I know the term is coined already but recently it came to my mind more than once:
Code that fit's in your head.
That's what I love about vertical slice architecture (wrt coupling and cohesion).
HTMX and Alpine are a nice fit due to locality of behavior.
Paired together with Event Sourcing (not having to guess what might have happened to the state) it gives me some peace of mind I've missed for a long time.
I want to introduce you to Emmett! Finally, I gathered the patterns around #EventSourcing and #CQRS I used last year and grouped them into a Node.js package.
I’m on the market for a staff/principal role. I have a passion for #SoftwareArchitecture, Developer Experience, community, mentoring, #performance, and interacting with business and domain experts.
I'm continuously trying to improve the way I teach #EventSourcing. Today, I reshaped my practical introduction workshop exercises. Previously, I got a few comments that there's a big jump between the first exercises and the one implementing business logic.
Thinking out loud: part of my thinking in how I am approaching #FeatherPub is what I started thinking of as the "boids model" of federated software development.
"But Hrefna, I sure as hell didn't hear about the 'boids model' in my SE classes"
Yes, this is just kind of my own colloquial thinking about it.
For those who are unaware, boids is an artificial life simulator based around the flocking behavior of birds. The idea is that we can simulate general flocking with a few basic rules.
Note that there's a whole interesting community of folks into #DDD#CQRS and #EventSourcing who moved away from Xitter onto the Fediverse.
I was just followed by @oskardudycz who is among those, maybe having seen this discussion?
What I would be very interested about is to get some expert opinions on how we might scale these architecture patterns and EDA and map it to our #SocialWeb.
A social web of interconnected components & services would be fabulous. #AppFreeComputing
I kept replaying events to rebuild the read models, only to realize that I forgot registering the view in question for all events that should be handled.
Fantastic experience when debugging results in higher confidence of your work 🙂
Any #dotnet developers out there using #CosmosDb for #EventSourcing, and have any general gotchas or must-do/must-avoid please? We’re looking at it but the team has little experience with it, and I’ve only ever heard disparaging comments around Cosmos. Thanks!
In this new #eventsourcing blog post we will considered several ways to implement state to be used in decision-making. We're equipped with a varied range of tools suitable for different sizes and maturity of problems, from deriving the state with #kotlin stream extension functions to employing finite state machines.
I'd love to work with a team already working with #EventSauce or a team wanting to bring EventSauce into their #php project.
An ongoing consulting relationship or a part-time/short-term contract would be my preference, but I would consider full-time employment for the right opportunity.
Please message me here or contact me via my website to talk more!
Do you know a good linkable reference article that has a good definition or explanation of the term *read model *in a #EventSourcing#CQRS#SoftwareArchitecture ?
I'm starting Office Hours this week! I've set aside time on Thursdays to connect with people to discuss software development, open-source software, architecture, and domain modeling.
I think that prototyping is an underestimated design skill. We immediately fall to whiteboard diagrams, sticky notes, or endless discussions when we think about the design.
But there's another way.
I showed that in my last article using the following ingredients: