PHP 7.4+ EventStore implementation providing common interfaces and classes for event sourcing.
Prooph Event Store is a PHP implementation of the EventStore pattern that provides common interfaces and classes for building event-sourced applications. It serves as the foundation for storing and retrieving domain events in chronological order, enabling developers to implement event-driven architectures with persistence capabilities. The project supports multiple connection protocols through separate client implementations.
PHP developers building event-sourced applications, particularly those working with domain-driven design (DDD) or implementing CQRS patterns. It's suitable for teams needing standardized event storage abstractions across different persistence backends.
Developers choose Prooph Event Store for its clean, standardized abstractions that provide consistency across implementations while maintaining flexibility. It's part of the established Prooph ecosystem, offering active support for modern PHP versions and multiple connection protocol options.
PHP 7.4 EventStore Implementation
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides common contracts for event store implementations, ensuring consistency across backends like TCP and HTTP clients, as highlighted in the key features.
Supports PHP 7.4+ with ongoing development for PHP 8.1+, as shown in the version guidance table, ensuring compatibility with modern PHP environments.
Designed to be extended with custom plugins and adapters, allowing flexibility for specific use cases, per the extensible architecture feature.
Serves as the core component in the Prooph ecosystem, facilitating integration with other event-driven tools for PHP developers.
The README states documentation 'will be published on the website soon,' making it difficult for new users to get started without external resources.
Requires separate client packages for persistence implementations, such as TCP or HTTP clients, adding complexity compared to all-in-one solutions.
Focuses on core abstractions without out-of-the-box features like event replay or snapshotting, which may require custom development or additional packages.