prooph/event-store

This system is a PHP-based event store client library that provides a modern, strongly-typed API for interacting with event-sourced systems. It supports core event store operations including connection management, stream and catch-up subscriptions, and persistent subscriptions, alongside management of projections and user accounts. The codebase has been significantly refactored to remove legacy adapters, deprecated interfaces, and outdated testing infrastructure, focusing instead on clean, type-safe interactions with the event store.

16 changes.

This period focused on the complete removal of the legacy Prooph EventStore component and its associated adapters, including support for Zend Framework 2. The project also modernized its development infrastructure by updating to PHP 8.1+, upgrading dependencies, and integrating static analysis and code style tools.

8 changes.

This period was dominated by the complete rewrite of the library for version 8, introducing a modern, strongly-typed API with new interfaces and value objects for connections, subscriptions, projections, and user management. Internal architecture was restructured to support persistent subscriptions and transaction handling, while utility classes for DateTime, Guid, and JSON were introduced to replace legacy implementations.

Added new immutable value objects—PersistentSubscriptionConfigDetails, PersistentSubscriptionConnectionDetails, and PersistentSubscriptionDetails—each providing structured access to configuration, connection, and overall subscription state. These classes expose properties such as resolveLinktos, messageTimeoutMilliseconds, averageItemsPerSecond, and connectionCount, enabling more granular inspection of persistent subscriptions. A corresponding PersistentSubscriptionsManager interface defines the contract for describing, listing, and replaying messages for persistent subscriptions.

src/PersistentSubscriptions · high confidence

The UserManagement namespace now includes value objects for user data and operations: ChangePasswordDetails, RelLink, ResetPasswordDetails, UserCreationInformation, UserDetails, and UserUpdateInformation, alongside the UsersManager interface that defines methods for creating, updating, enabling, disabling, and deleting users, as well as retrieving user details and managing passwords.

src/UserManagement · high confidence

The Projections namespace now introduces a new set of classes and interfaces for managing projections and executing queries. This includes the ProjectionsManager and QueryManager interfaces, which provide methods to enable, disable, abort, create, and delete projections, as well as to list and retrieve their status, state, and statistics. Additionally, new value objects like ProjectionDetails, ProjectionStatistics, Query, and State are introduced to represent projection metadata and query results, enabling users to interact with the event store's projection system through a more structured and typed API.

src/Projections · high confidence

The src/Util directory now contains three new utility classes: DateTime, which provides static methods for creating and formatting DateTimeImmutable objects; Guid, which wraps the Ramsey UUID library to generate, parse, and format UUIDs; and Json, which offers static methods for encoding and decoding JSON with specific flags like JSON\_THROW\_ON\_ERROR. These classes replace previous implementations or inline code with dedicated, reusable utilities.

src/Util · high confidence

The \src\ directory has been completely rewritten for version 8, introducing a new set of interfaces and value objects that define the event-store contract. This includes new interfaces for managing connections (\EventStoreConnection\), subscriptions (\EventStoreSubscription\, \EventStoreCatchUpSubscription\, \EventStoreAllCatchUpSubscription\, \EventStoreStreamCatchUpSubscription\, \EventStorePersistentSubscription\), and transactional writes (\EventStoreTransaction\). The update also introduces numerous new value objects and enums to replace previous patterns, such as \AllCheckpoint\, \AllEventsSlice\, \CatchUpSubscriptionSettings\, \ConditionalWriteResult\, \DeleteResult\, \EndPoint\, \EventReadResult\, \EventReadStatus\, \ExpectedVersion\, \PersistentSubscriptionSettings\, and various status enums like \ConditionalWriteStatus\ and \PersistentSubscriptionCreateStatus\. These changes provide a more strongly-typed and structured API for interacting with the event store.

src · high confidence

The Zf2EventStoreAdapter class has been removed from the codebase. This adapter previously provided event store persistence for the Zend Framework 2 ecosystem, including schema creation and event loading/writing functionality. Its removal indicates that support for this specific adapter is no longer maintained or required.

src/Prooph/EventStore/Adapter/Zf2 · high confidence

The \Prooph\\EventStore\\Adapter\\AdapterInterface\ and \Prooph\\EventStore\\Adapter\\Feature\\TransactionFeatureInterface\ have been removed from the codebase. This eliminates the legacy adapter contract and the specific transaction feature interface that the \EventStore\ class previously relied on for transactional support.

src/Prooph/EventStore · high confidence

The \Prooph\\EventStore\\Configuration\\Configuration\ class and its associated \ConfigurationException\ have been removed from the codebase. This change eliminates the previous mechanism for configuring the event store adapter and repository mappings via a configuration array, indicating a shift in how the event store is initialized and configured within the application.

src/Prooph/EventStore/Configuration · high confidence

The src/Internal directory has been restructured with the addition of several new internal classes and interfaces to support persistent subscriptions, transaction handling, and client event management. Specifically, ConnectToPersistentSubscriptions and EventStoreTransactionConnection define internal interfaces for subscription operations and transactional writes. PersistentEventStoreSubscription implements the subscription logic, delegating to the new interface. A new EventHandler class manages client connection lifecycle events (connected, disconnected, reconnecting, closed, error, authentication failed) by attaching and detaching ListenerHandler callbacks. Additional internal classes include Consts for configuration defaults, DateTimeStringBugWorkaround for date formatting, DropData for subscription drop reasons, and ResolvedEvent for event resolution. These changes represent an internal architectural shift to better separate concerns in the event store client implementation.

src/Internal · high confidence

The exception classes in the \src/Exception\ directory have been moved from the legacy \Prooph\\EventStore\\Exception\ namespace to the modern \Prooph\\EventStore\\Exception\ namespace, aligning with PSR-4 autoloading standards. This change updates the namespace declarations and file locations for all exception types, including \EventStoreException\, \RuntimeException\, \InvalidArgumentException\, and specific error classes like \AccessDenied\, \ConnectionClosed\, and \WrongExpectedVersion\, ensuring consistent error handling across the library.

src/Exception · high confidence

The \AggregateChangedEvent\, \EventSourcedAggregateRoot\, and related exception classes (\IdentifierPropertyNotFoundException\, \NoHandlerFoundException\) have been removed from the \Prooph/EventStore/EventSourcing\ namespace. Additionally, the \DetermineEventHandler\ and \GetIdentifierProperty\ lifecycle event classes in \Prooph/EventStore/LifeCycleEvent\ have been deleted. This change eliminates the previous mechanism for automatically mapping and dispatching domain events to aggregate roots, requiring users to adopt a different approach for handling event sourcing and lifecycle events.

src/Prooph/EventStore/EventSourcing, src/Prooph/EventStore/LifeCycleEvent · medium confidence

The \EventSourcingRepository\ class and the \RepositoryInterface\ interface have been removed from the \src/Prooph/EventStore/Repository\ directory. This eliminates the previous concrete implementation and its contract for managing event-sourced aggregates, signaling a shift in how the event store handles aggregate persistence.

src/Prooph/EventStore/Repository · high confidence

The \AdapterException\ interface and the \ConfigurationException\ and \InvalidArgumentException\ classes in the \Prooph\\EventStore\\Adapter\\Exception\ namespace have been removed from the codebase. This eliminates the custom exception hierarchy for adapter-related errors, which may affect code that relied on these specific exception types.

src/Prooph/EventStore/Adapter/Exception · high confidence

The \AggregateRootDecorator\ and \OnEventNameHandlerStrategy\ classes have been removed from the \Prooph\\EventStore\\Mapping\ namespace. These classes previously handled aggregate root decoration and event name resolution for the event store, and their removal indicates a refactoring of how the event store maps and processes events.

src/Prooph/EventStore/Mapping · high confidence

The \AggregateIdBuilder\, \AggregateIdType\ interface, and \EventBuilder\ classes in \src/Prooph/EventStore/Adapter/Builder\ have been removed. These classes previously handled aggregate ID string conversion and event reconstruction via reflection, but are no longer part of the codebase.

src/Prooph/EventStore/Adapter/Builder · high confidence

The project's continuous integration setup has been modernized: the Travis CI configuration now targets PHP 7.4 and 8.0, includes a build matrix for lowest/stable dependencies, and integrates Psalm for static analysis and php-cs-fixer for code style checks. Additionally, a new \.coveralls.yml\ file was added to configure code coverage reporting, and the \phpunit.xml.dist\ configuration was updated to enable error-to-exception conversion for more robust test execution.

(repo-wide) · high confidence

Added test coverage for DateTimeStringBugWorkaround; Removed ZF2 Event Store adapter tests; Removed legacy test bootstrap and configuration files; Removed mock domain classes from test suite; Removed obsolete EventSourcingRepositoryTest; Removed obsolete test for AggregateRootDecorator; Removed obsolete test suite for the Prooph EventStore.

The project now requires PHP 8.1 or higher, removing support for all previous PHP versions. Dependencies have been significantly updated: 'ramsey/uuid' is updated to ^3.9.3, 'phpunit/phpunit' to ^9.6 \|\| ^10.0, and 'doctrine/instantiator' to ^1.4 \|\| ^2.0. Additionally, 'amphp/amp' is added as a dev dependency, and the 'zendframework' packages are removed entirely. The autoload configuration is also updated from PSR-0 to PSR-4.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 57 → 59 (+1.3)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (-0.1)
• Architecture 100 → 98 (-1.7)
• Maturity 34 → 34 (+0.0)
• Readiness 61 → 65 (+4.1)
• Security 92 → 95 (+2.7)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Test reliability not included
• The README states 'prooph/event-store' provides 'common classes and interface for Prooph Event Store implementations' (README.md)
• dormant codebase — no living knowledge left to concentrate

• Dependency hygiene PARTLY measured — Composer dependencies read, no committed lock to grade for currency
• Documentation: no architecture or design documentation (README.md)
• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (28 lines × 2) (src/RawStreamMetadataResult.php)
• Inconsistent builder method naming for setting the consumer strategy. Two methods use 'prefer' prefix, while the third uses 'withNamedConsumerStrategy'. This breaks the fluent builder pattern's consistency.
• Inconsistent naming for bulk operations. The API provides 'acknowledge' (single), 'acknowledgeMultiple' (array of events), 'acknowledgeEventId' (single ID), and 'acknowledgeMultipleEventIds' (array of IDs). The naming convention switches between 'Multiple' and 'MultipleEventIds' inconsistently. It should be 'acknowledge', 'acknowledgeEvents', 'acknowledgeEventIds', or 'acknowledgeMultiple' for all bulk operations.
• Inconsistent naming for directional read operations. One uses 'Forward' and the other 'Backward', but the parameter 'start' has ambiguous semantics depending on direction (is it the first event to read, or the last event to read?). Furthermore, 'readAllEventsForward' and 'readAllEventsBackward' exist, but there is no 'readAllEvents' generic method, forcing the caller to know the direction. More critically, the subscription methods 'subscribeToStream' and 'subscribeToStreamFrom' are confusingly named; 'subscribeToStream' implies starting from the beginning or current, while 'subscribeToStreamFrom' implies a specific checkpoint, yet both are stream subscriptions. The naming does not clearly distinguish between 'live-only' and 'catch-up' semantics.
• Redundant 'Raw' vs 'Typed' API surface. The library exposes both a typed 'StreamMetadata' object and a 'Raw' string-based API for the same underlying concept. While this might be for backward compatibility or performance, it creates a confusing dual API where the user must choose between a structured object and a raw string. The 'Raw' variants are essentially wrappers around the same operation with different serialization/deserialization steps, which should ideally be handled internally or via a single fluent API.
• Same inconsistency as acknowledge: 'fail' vs 'failMultiple' vs 'failEventId' vs 'failMultipleEventIds'. The pattern is inconsistent with the acknowledge methods and internally inconsistent itself.

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

prooph/event-store was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.