Today's stream starts at 20:00 UTC, shortly after the Spring Boot 3.4.0 release party.
Join me for mistakes, thoughtful pauses, head-scratching, a rant or two, and maybe some actual #Java coding of an #EventSourced game using #HTMX and #SpringBoot, all done with #TDD.
Today's stream starts earlier than usual at 20:00 UTC, cuz it's raining.
Join me for lots of mistakes, puzzled looks, rants, and maybe some actual #Java coding of an #EventSourced game using #HTMX and #SpringBoot, all done with #TDD. (is that enough hashtags?)
We've arrived! An example of #eventSourced user management in #fsharp using #marten awaits you in the newest post in my dev journal series: https://blog.mavnn.co.uk/2024/03/05/dev_journal_4_2.html
A website that users can sign up for and log in to. Exciting stuff.
Also, I am currently the world's only expert in the "julienned domain sandwich" architecture style, so you should probably hire me to help you implement it in your project.
Thanks to the @team for the hard work and the beta version of the new #eventsourced #neoscms 🥳🍾
in this post i write about and show how to merge #aggregates in #eventSourced systems (particularly with the #dolittle #sdk)
i've blogged again - this time about #generating #eventSourced #domainDriven #code in c# using the #dolittle #sdk with #chatGPT
Where a single command gives rise to more than one event (in an #eventsourced system) you can design the order in which you emit those component events.
The (accidental?) conflation of #eventsourced and #eventdriven systems is going to be a major problem in the year ahead...
No surprise that implementing such a feature is really straight forward in an #eventsourced system. Everything feels natural.
Iterate through the event stream, count the number of finishes cards (tasks), memorize which achievements were already granted, check the specs and produce a new event if a new achievement (or level) was reached.
Should we want to introduce temporal achievements like „finished tasks per week“ - easy peasy, the time is in the events.
3/x
Turns out, I have not really declared my huge 💛 for #eventsourcing since I‘m on Mastodon. 😺
We‘re building a company-internal social card game @MaibornWolff with #golang - and it’s #eventsourced
If you want to learn about the #domainlogic of the game, I described it here:
After many busy months I was finally able to work on the game again, mostly while spending ~10 hours in the 🚆
1/x
The complication of adding features to a #CQRS and #Eventsourced system scales linearly.
CRUD starts from a lower base but the complication scales near exponentially because the state model resists change.
Read models in event sourcing:
- You can have more than one
- They can be denormalised
- They are always out of date
#eventsourced thoughts...
I wonder if there are any aspects of model based development that people miss when they are doing #eventsourced systems?
(And, if so, can these be recreated on top of a #ES system?)
Wrote an article on how to improve your Spreadsheets with Event Sourced architecture.
With demo spreadsheet and background on #eventsourced architecture.
"Event Source your Spreadsheets for Flexibility and Maintainability"
https://berk.es/2022/08/16/event-source-your-spreadsheets-for-flexibility-and-maintainability/
Once I learned #eventsourced architecture, I realized that several systems which I wrote in the past, suffered because they weren't event sourced.
It's one of those "if only I knew back then" architectures.
Would be so cool if also package maintainers adapt that branching scheme … then people could easier try the new #eventsourced content repository with projects. #neoscms
