You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning to create v2 of NEventLite soon and there will be some breaking changes. It's not formalized yet but I plan to do the following.
Move Commands, CommandHandler and ExternalEventHandlers out of the core project as they aren't a critical part of the workflow.
Add support for custom Id data type like (Guid, Int or String) for Aggregates and Events.
Add support for async (internal) event handlers.
My goal for NEventLite is not to be a full framework that solves every problem but rather solves one particular problem well. It will act as a library that allows you to manage the lifecycle of your aggregates in an event sourced system. You can use the plethora of other (OSS and paid) Command dispatching libraries to create a command pipeline and do the same when you need to dispatch events over the cloud. NEventLite will plugin and work with any of these solutions.
I'm planning to create v2 of NEventLite soon and there will be some breaking changes. It's not formalized yet but I plan to do the following.
My goal for NEventLite is not to be a full framework that solves every problem but rather solves one particular problem well. It will act as a library that allows you to manage the lifecycle of your aggregates in an event sourced system. You can use the plethora of other (OSS and paid) Command dispatching libraries to create a command pipeline and do the same when you need to dispatch events over the cloud. NEventLite will plugin and work with any of these solutions.
The old version can be found here https://github.com/dasiths/NEventLite_legacy
The text was updated successfully, but these errors were encountered: