event-store

问题 How can I access all stored events in the EventStore to rebuild my read models? A method called GetFrom is mentioned at question J Oliver EventStore V2.0 questions, but I cannot find this method on the interface "IStoreEvents" which is returned from Wireup. 回答1: That method is a part of the IPersistStreams interface and not the IStoreEvents interface. The API needs to be refined slightly to accommodate that. I have just added a method to IStoreEvents called GetFrom(DateTime started) that

问题 I'm looking for good examples of testing the domain using JOlivers CommonDomain and EventStore I have been watching greg youngs videos and he has a nice simple abstract aggregate root test fixture. is there anything like that which can be used with these libs? 回答1: Edit: due to the immaturity of and forced inheritance in CommonDomain, Documently/develop now rolls its own simpler EventRouter Yes, I have a sample here: https://github.com/haf/Documently that shows how you can use it together and

问题 Using the MongoDB persistance engine in joliver/EventStore causing the error Unknown discriminator value 'MyEvent' . The issue is only caused when I try to load all events for replaying the events like this.storeEvent.Advanced.GetFrom(new DateTime(2010, 1,1)) The issues is caused in ExtensionsMethods.cs public class MyClassEvent : IDomainEvent { ... } public static Commit ToCommit(this BsonDocument doc, IDocumentSerializer serializer) { if (doc == null) return null; var id = doc["_id"]

问题 Hypothetically I'm working on a system that uses "Event Sourcing" (storing the business events) that has purchase and selling of materials; at some point a report, with prices and costs information is generated. Imagine that one of my clients call me and says, "The costs are wrong, for me, the rules from profit are this way". I could add more handlers or change the rules to adjust to this particular case, and replay the events. But my question is, this is the correct approach (or at least the

问题 I have a project which is designed or at least should be according to the well known DDD principles. Back - DDD + CQRS + Event Store UI - ngrx/store I have a lot of questions to ask about it but for now I will stick to these two: How should the UI store be updated after a single Command/Action is executed ? a) subscribe to response.ok b) listen to domain events c) trigger a generic event holding the created/updated/removed object ? Is it a good idea to transfer the whole aggregate root dto

问题 I have a project which is designed or at least should be according to the well known DDD principles. Back - DDD + CQRS + Event Store UI - ngrx/store I have a lot of questions to ask about it but for now I will stick to these two: How should the UI store be updated after a single Command/Action is executed ? a) subscribe to response.ok b) listen to domain events c) trigger a generic event holding the created/updated/removed object ? Is it a good idea to transfer the whole aggregate root dto

问题 Using JOliver EventStore 3.0, and just getting started with simple samples. I have a simple pub/sub CQRS implementation using NServiceBus. A client sends commands on the bus, a domain server recieves and processes the commands and stores events to the eventstore, which are then published on the bus by the eventstore's dispatcher. a read-model server then subscribes to those events to update the read-model. Nothing fancy, pretty much by-the-book. It is working, but just in simple tests I am

问题 Using JOliver EventStore 3.0, and just getting started with simple samples. I have a simple pub/sub CQRS implementation using NServiceBus. A client sends commands on the bus, a domain server recieves and processes the commands and stores events to the eventstore, which are then published on the bus by the eventstore's dispatcher. a read-model server then subscribes to those events to update the read-model. Nothing fancy, pretty much by-the-book. It is working, but just in simple tests I am

问题 I've moved to the project which is actively using CQRS + event sourcing. From the first glance it's implemented in accordance with all those books and blogs, but finally I realized what exactly is peevish in the implementation. Here is CQRS architecture: Originally I took this picture from here. As we can see in the picture, the read side receives events from the queue and passes it one by one into different sets of projections(denormalizers) and then resulting ViewModels are saved through

问题 Trying to wire up JOliver's EventStore with RavenDB and hit a snag. I created a new DB in Raven called RavenEventStore. The following is my wireup; return Wireup.Init() .UsingRavenPersistence("RavenEventStore") .UsingAsynchronousDispatchScheduler() .DispatchTo(new DelegateMessageDispatcher(DispatchCommit)) .Build(); When the Wireup.Init() is called, this exception is occuring on the RavenDb side; Url: "/indexes/RavenCommitByDate" Newtonsoft.Json.JsonReaderException: Unexpected character