Call me crazy, but I firmly believe that Commands (DTOs) in a #CQRS application are part of the domain.
They are the imperative that is given by the stakeholder.
Yes, you will have infrastructure commands like "clean up some tables", but "sudo make me a sandwich" is business domain.
If you're in an industry long enough, you'll see the same trends pop up again and again, sometimes just with different names. This post is basically advocating for #CQRS (command query request segregation), a practice that many of us in the #php community were using over 10 years ago, but giving it a new name for Laravel users.
Would you be interested in a blog post about using event-sourcing with API Platform?
I'm thinking about diving into how this could work with API Platform, leveraging its powerful tools for building modern APIs while keeping event-driven persistence in mind.
Would this be something you’d like to read about? Or do you have specific challenges or questions around event-sourcing and API Platform? Let me know!
I've been pondering about creating EventSourcing, CQRS & DDD scaffolding from scratch in TypeScript.
There doesn't seem to be an OpenSource basic scaffolding for this using RxJS? ( I mean the basic bang like NgRx ).
DDD -> NgRx
- Command -> Action ( in imperative )
- Command Handler -> Effect
- Domain Event -> Action ( in past tense )
- Aggregate state -> a Store entry
- Aggregate state's apply -> Reducer
Did I get this right?
I just copied that article (from 2022) to Substack ...
(not paywalled there)
Event Sourcing explained
https://open.substack.com/pub/eventsandstuff/p/event-sourcing-explained
Just published:
Unraveling CQRS, Event Sourcing, and EDA - Part 3: Event-Driven Architecture
#microservices #eventdrivenarchitecture #cqrs #eventsourcing
On Medium, so paywalled.
Still searching for an additional (non-paywalled) site.
Just published - the 2nd part of my series on Medium via #ITNEXT
Unraveling CQRS, Event Sourcing, and EDA - Part 2: Event Sourcing
https://itnext.io/unraveling-cqrs-event-sourcing-and-eda-part-2-event-sourcing-434404e035f0
Hey folks!
I‘m looking for new professional opportunities from February 25 on!
If your org is hiring or you have recommendations … shoot me a message, please! 
#dddesign #golang #hexagonal #eventsourcing #cqrs #eventdriven #tdd
Reposts very much appreciated! 
I'm searching for a new professional opportunity from February on, an earlier start is possible but I'm not in a rush!
I bring along 25+ years of experience as a software developer, architect, team lead, learning designer (trainer).
Please share! :-)
Some of my skills and interests:
#golang #dddesign #hexagonal #portsandadapters #collaboration #agile #eventsourcing #cqrs
Slides for my talk "DoneThat with Fyne, DDD, EventSourcing, and CQRS" last Friday at #FyneConf 2024:
After more than a year of intense work with #EventSourcing and #CQRS, other models feel... different... kind of wrong. Why? The gymnastics to make a single storage representation work for all use-cases is just crazy. #SoftwareDevelopment #SoftwareEngineering
Op de #dagVanHetWiezen, 30 mei, geef ik een inleiding over #EventSourcing en #Cqrs, aan de hand van onze score-app voor het #wiezen, #dikdikdik.
Iedereen welkom, maar wel even inschrijven aub: https://www.meetup.com/coven-of-wisdom-herentals/events/299483634/ (Talk in het Nederlands, hoewel de meetup-page in het Engels is) #covenOfWisdom
"Code that reads data should not write data, and code that writes data should not read data." - #cqrs in a nutshell. Via @grmpyprogrammer.
There's a lot going on at the #Java User Group Switzerland this week! On Tuesday, @SimonMartinelli will talk about #CQRS on a small scale with Java #Records and #jOOQ in #Bern (
), on Wednesday @ixchelruiz is organizing a meeting with the tech community in #Basel to celebrate #IWD (International Women's Day) (
), and on Thursday we'll be following in the footsteps of architectural art with Meteo Switzerland in #Zurich (), followed by our annual general meeting (). Looks like a busy week!
the focus was on solving business challenges while designing with some technological constraints in mind. The organization uses the leading #ERP, which offers standard functionality out-of-the-box to support many business processes. The new design targets the #cloud, using #cloudnative services to build a #CQRS and #EventSourcing application.
2/7
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.
Check the docs: https://event-driven-io.github.io/emmett/!
Why Emmett? Because I'd like to take your event-driven tooling back to the future!
The goal is to help reduce the boilerplate, enhance strong sides and help you skip common mistakes.
1/
I've pondered similar thoughts since I watched Greg Young's "The Art of Destroying Software".
I really think #EventSourcing is part of the puzzle as well as #cqrs.
Our industry keeps looking elsewhere. It's good to have people like Adam who have the energy to go their own way.
In my opinion, if you architected your system in a way the code quality doesn't matter, you have achieved good code quality.
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 ?
Pracuję nad kursem online #DDDesign #CQRS i #EventSourcing na platformę #Java opartym na moim PRODUKCYJNYM doświadczeniu:
"DDD/CQRS/ES applied on JVM with Axon Framework"
Jeśli jesteś Programistą, Team Leaderem, lub Architektem i chcesz W KOŃCU wprowadzić je do Twojego systemu, dołącz już dziś do listy oczekujących, pobierz darmowy Ebook:
"4 narzędzia do DDD/CQRS/ES na platformie Java"
(Plus jedno, błędnie za takie postrzegane - BONUS!)
i bądź na bieżąco:
PLS Boost
