neventstore

Event Up-Conversion With Keeping Event-Class Name

由 六眼飞鱼酱① 提交于 2020-01-02 06:43:45
问题 NEventStore 3.2.0.0 As far as I found out it is required by NEventStore that old event-types must kept around for event up-conversion. To keep them deserializing correctly in the future they must have an unique name . It is suggested to call it like EventEVENT_VERSION . Is there any way to avoid EventV1 , EventV2 ,..., EventVN cluttering up your domain model and simply keep using Event ? What are your strategies? 回答1: In a question long, long time ago, an answer was missing... In the

NEventStore issue with replaying events

由 倖福魔咒の 提交于 2020-01-01 09:43:22
问题 We are using CQRS + ES. The ES is NEventStore (folrmerly JOliver EventStore). We have 2 aggregates in different commands. The projections of the second AR depends on the data written by the first AR projections in the read model. The problem is that when we run the software everything goes so fast that sometimes the two aggregates are persisted in the event store with identical datetime (column CommitStamp). When replaying the events we get them from the beginning ordered by CommitStamp

EventStore + RavenDB, not deserializing correct

由 家住魔仙堡 提交于 2019-12-08 04:16:32
问题 Trying out JOliver CommonDoman/EventStore 3.0 with RavenDB, where it works fine to store events, but when trying to load an aggregate root with IRepository.GetById() there is an issue in deserialization. Giving the error message "Unable to cast object of type 'Raven.Abstractions.Linq.DynamicList' to type 'System.Collections.Generic.List`1[EventStore.EventMessage]'." at DocumentObjectSerializer.cs, public T Deserialize<T>(object document) { Logger.Verbose(Messages.DeserializingStream, typeof(T

Event Up-Conversion With Keeping Event-Class Name

由 非 Y 不嫁゛ 提交于 2019-12-05 17:19:20
NEventStore 3.2.0.0 As far as I found out it is required by NEventStore that old event-types must kept around for event up-conversion. To keep them deserializing correctly in the future they must have an unique name . It is suggested to call it like EventEVENT_VERSION . Is there any way to avoid EventV1 , EventV2 ,..., EventVN cluttering up your domain model and simply keep using Event ? What are your strategies? In a question long, long time ago, an answer was missing... In the discussion referred in the comments, I came up with an - I would say - elegant solution: Don't save the type-name
订阅 neventstore