-
Because some code generated projects are dependent on others - for example [IdentityGroup] depends on the event definitions in [EventSourcing] some duplicate class definitions occur if files are inclu…
-
It would be very nice if the container (and so the start up script) would support the creation of topics like the wurstmeister/kafka container does, i.e. "--env KAFKA_CREATE_TOPICS=eventsourcing-traff…
-
This tasks refers to how in this project data should be queried from.
This flow should be universal and used for all the queries.
It can be:
- CQRS with Mediatr. Basically separating all the re…
-
- Stream stage that uses event handler to create and emit state snapshots and metadata at custom intervals
- Initialize `EventSourcing` stage with state snapshot
- Replay events from user-defined po…
-
When state is needed after a command, check if created event was successfully applied, and eventstore returned a beautiful OK that the event was persisted, so in terms of latency, you have now the mos…
-
Hi dear author and all participants, I am still quite new to the whole DDD/Event-sourcing architecture as well as this library, but I do get the idea of the `event recording and replay` idea. But my q…
-
It seems odd to snapshot the event sourced grain state to IGrainStorage on every write, what was the rational behind that?
It would be nice to have that behaviour be opt-in, and ideally something …
-
-
How to comply with GDPR regulations which require personally identifiable information (PII) to be removed upon request. This is problematic with immutable, persistent event streams.
There are three…
-
Distributed systems; how can node help? :grin:
**Suggested topics**
- what is a distributed system?
- why is it relevant?
- why node?
- p2p
- dht
- scuttelbot
- ipfs
- hyperfs
- peernet (gossip)
- s…