event-store

PHP 7.4 EventStore Implementation

BSD-3-CLAUSE License

Downloads
1.3M
Stars
548
Committers
35
event-store - 7.0.0-beta1 Release

Published by prolic almost 8 years ago

event-store - 6.5.1 Release

Published by prolic almost 8 years ago

Added

  • nothing

Removed

  • nothing

Fixed

Note: The event-store now uses an AppendIterator internally, so I could be that it breaks for you, when you extended the event-store. In this case you can easily revert this change yourself. See: https://github.com/prooph/event-store/pull/208

event-store - 6.5.0 Release

Published by prolic almost 8 years ago

Added

Removed

  • nothing

Fixed

  • nothing
event-store - 6.4.0 Release

Published by prolic almost 8 years ago

Added

Removed

  • nothing

Fixed

  • Event Store tests
event-store - 6.3.0 Release

Published by codeliner over 8 years ago

#Added

  • #173 add concurrency exception
event-store - 6.2.0 Release

Published by codeliner over 8 years ago

Added

Changed

event-store - 6.1.2 Patch Release

Published by codeliner over 8 years ago

Changed

  • #166 Move ramsey/uuid to require-dev
event-store - 6.1.1 Bugfix Release

Published by codeliner over 8 years ago

Fixed

  • #161 Set recordedEvent back to ArrayIterator when rolling back transaction
  • #160 Housekeeping
event-store - 6.1 Release

Published by codeliner over 8 years ago

Added

  • #154 patch aggregate repository to allow inheritance aggregate roots, see the new docs page for details
event-store - 6.0 Release

Published by codeliner almost 9 years ago

Summary

The 6th major release of prooph/event-store adds a lot of great new features like snapshot support, replay functionality and using stream iterators to be able to handle huge amount of events when loading streams.
Interface changes and removed classes cause some BC breaks. We recommend you to read documentation. Also new versions of the event store adapters are released. Make sure you require the newest version for your adapter of choice.

If you're using prooph event store together with prooph/event-sourcing just update prooph/event-sourcing to v4.0 and maybe align your repositories set up.

If you encounter any problems with upgrading to prooph/event-store v6.0 don't hesitate to contact us in the prooph chat. We are glad to support you.

Added

#13, #104 - Replay functionalitiy
#26 - Notes about upcasting
#113 - Snapshotting

Changed

  • #116 Factories make use of interop-config
  • #101, #138 AggregateTranslator contract
  • #98 Implement event stream as an iterator
  • #140 Clear identity map on commit.post
  • #127 Use event store FQCN as service id

Removed

  • #97 Deprecated nested transaction support is now removed
  • #142 Stream strategies are gone, repository set up is much simpler now
event-store - 6.0-beta.1 Release

Published by codeliner about 9 years ago

This is a pre release for the upcoming changes in prooph/event-store v6 and related compontents.
The following list contains the most important changes. A detailed changelog will be added to the final v6 release.

event-store - 5.1 Release

Published by codeliner about 9 years ago

Added

  • #94 It is now possible to ask the event store if it is in active transaction with EventStore::isInTransaction(): bool
event-store - 5.0 Release

Published by codeliner about 9 years ago

Added

  • Factories which help you set up the event store and related components
    • the factories support interop-container for framework interoperability
  • ConfigurableAggregateTranslator, see new documentation
  • Package specific exceptions extending core exceptions
  • Tons of tests

Changed

  • event store now only requires Prooph\Common\Messaging\Message interface instead of domain event implementations
  • Nested transactions are marked as deprecated and will be removed with prooph/event-store 6
  • Constructor signature of AggregateRepository, see #72
  • Feature interface renamed to Plugin
  • If event store should perform a rollback but the used adapter does not support transactions an exception is thrown
  • InMemoryAdapter is no longer used as the default adapter, you have to instantiate (or configure) the adapter you want to use

Removed

  • ZF2 dependencies
    • PostCommitEvent and PreCommitEvent
      • now Prooph\Common\Event\ActionEvents are triggered and you have to use getParam method to access for example all recorded events
    • FeatureManager the logic is now handled by the EventStoreFactory
  • Configuration class, set up is handled by the EventStoreFactory
  • DomainEventMetadataWriter as Prooph\Common\Messaging\Messages now provide withMetadata and withAddedMetadata methods
  • DefaultAggregateTranslator in favour of the new ConfigurableAggregateTranslator
event-store - 5.0-beta.3 Release

Published by codeliner about 9 years ago

Third 5.0 beta release includes some bugfixes and 100 % test coverage

event-store - 5.0-beta.2 Release

Published by codeliner about 9 years ago

Second beta release.

An overview of all upcoming changes can be found here

event-store - 5.0-beta.1 Release

Published by codeliner over 9 years ago

Summary of changes can be found in #50

event-store - 2.1.1 LTS Bugfix Release

Published by codeliner over 9 years ago

Fixed

  • #44 - Reset recorded events

We decided to provide LTS for prooph/event-store v2.x based on a request from @dottorbabba
thx again

event-store - 4.0.1 Release

Published by codeliner over 9 years ago

Fixed

  • #44 - Recorded events are now reset before EventStore.PostCommitEvent is triggered
event-store - 4.0 Release

Published by codeliner over 9 years ago

Changed

  • #42 adds support for nested transactions
    This is a BC break because in versions < 4 an exception was thrown when EventStore::beginTransaction was called within an active transaction. Also event triggering was aligned:
    • EventStore.beginTransaction is triggered for each EventStore::beginTransaction call. The event provides two new parameters with information about the current transaction level: (bool) isNestedTransaction and (int) transactionLevel
    • EventStore.commit.pre is triggered for each EventStore::commit call. It provides the same new parameters as the beginTransaction event
    • EventStore.commit.post is only called once after all transactions of the current session are committed. Thus you can continue to attach a DomainEventDispatcher to this event to publish events after they are really committed to the database
event-store - 3.1 Release

Published by codeliner over 9 years ago

Changed

  • Support prooph/common 2.0