Download the PHP package dsantang/domain-events without Composer
On this page you can find all versions of the php package dsantang/domain-events. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dsantang/domain-events
More information about dsantang/domain-events
Files in dsantang/domain-events
Package domain-events
Short Description A simple package that enables creation and caching of domain events.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package domain-events
Domain Events
A simple package that guides the creation and dispatching of domain events.
Installation
The suggested installation method is via composer:
Usage
This package is meant to provide an abstraction for your application's domain events. Domain events are events that can be raised by your Aggregates during a domain transaction. They capture an occurrence of something that happened in your domain. An example of a domain event is as follows:
Aggregate deletions
Sometimes the deletion of an aggregate is a relevant event too. In this case tho, the aggregate cannot throw the event
itself since it is most likely being deleted by your ORM.
To work around this problem, you can implement the DeletionAware interface to signal your ORM that the deletion of that
aggregate should raise an event.
Using transactions
Domain events can, and should, be momentarily cached in your aggregate, waiting until the transaction is completed. Once the transaction is finished, and your aggregate state has correctly been persisted in your data storage, the domain events that have occurred should be properly dealt with by your application.
In order to momentarily cache/retrieve those events in your aggregate, you can rely upon the simple EventsRegistry trait
provided by this library.
Example:
Since every application has its own way of persisting the state of aggregates, this library doesn't provide an automated way to dispatch those events, and it's up to the implementor to do that.
Those using Doctrine's ORM can rely upon an out of the box event dispatching automation,
which only kicks in once a Doctrine's transaction is completed.
The package name is:
