EventSourcing.NetCore
EventSourcing.NodeJS
Our great sponsors
| EventSourcing.NetCore | EventSourcing.NodeJS | |
|---|---|---|
| 8 | 3 | |
| 3,230 | 368 | |
| - | - | |
| 8.1 | 8.7 | |
| 4 days ago | 3 months ago | |
| C# | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
EventSourcing.NetCore
-
Hitchhiker's Guide to Moving from Relational Data to Events
https://www.youtube.com/watch?v=uODSwR2CIV4
He also maintains samples on GitHub:
https://github.com/oskardudycz/EventSourcing.NetCore
-
Best tutorial on Event Sourcing with ASP.NET Core?
I saw https://github.com/oskardudycz/EventSourcing.NetCore recently but haven’t explored. Maybe people here could take a look and confirm if it’s useful.
-
Guide to Projections and Read Models in Event-Driven Architecture
You’re welcome. If you don’t have the chance to do it in your project. You can play with my self-paced kit: https://github.com/oskardudycz/EventSourcing.NetCore/tree/main/Workshops/IntroductionToEventSourcing 🙂
- Practical Samples and Tutorials of Event Sourcing in .NET
-
Event Sourcing Is Hard
I have not watched that clip, but as I said above, Confluent isn't a good resource for defining this term since Kafka cannot be used to do ES. I would suggest an article like: https://domaincentric.net/blog/eventstoredb-vs-kafka
Also refer to the list of great resources @oskar_dudycz posted in another comment: https://github.com/oskardudycz/EventSourcing.NetCore#1319-th...
- Recommended Event Sourcing Frameworks?
EventSourcing.NodeJS
- Hitchhiker's Guide to Moving from Relational Data to Events
- Self-Paced Kit: Introduction to Event Sourcing with Node.js and TypeScript
-
Architecture patterns, decisions to make complex system more transparent (easier to debug)? Event-driven maybe?
Thanks for the response, I found materials for event sourcing with node.js examples (here) and will read more about it. Before diving in, the things you say sounds crazily complex, so one of the two: or it's in fact easier than I'm imagining, or it must be justified by crazily complex system which becomes a hell to maintain.
What are some alternatives?
Akkatecture - a cqrs and event sourcing framework for dotnet core using akka.net
fmodel-ts - Functional Domain Modeling with Typescript
dotnet-ci-pipelines - dotnet ci cd pipelines for github, azure devops, gitlab, bitbucket, and etc.
postgresql-event-sourcing - A reference implementation of an event-sourced system that uses PostgreSQL as an event store built with Spring Boot. Fork the repository and use it as a template for your projects. Or clone the repository and run end-to-end tests to see how everything works together.
Streamstone - Event store for Azure Table Storage
DDD-NoDuplicates - Some design approaches to enforcing a business rule requiring no duplicates. Domain driven design.
blog-articles
EventFlow - Async/await first CQRS+ES and DDD framework for .NET
example-modules - Example PrestaShop modules
m-r - Simple CQRS example
WizardWorldAPI - Source code for fan API for WizardWorld
proposals - Temporal proposals