How do I test an event-sourced aggregate with Broadway?

Broadway provides testing helpers specifically for aggregates, allowing you to simulate commands and assert event emissions. Check the documentation on broadway.github.io for examples and step-by-step guides.

Broadway vs Symfony for event sourcing?

Broadway is a specialized CQRS/ES infrastructure toolkit, while Symfony is a full-stack framework. Broadway can be integrated with Symfony via bundles, but it's better suited for domain-driven design scenarios requiring explicit event sourcing.

Is Broadway good for microservices architecture?

Yes, Broadway's decoupled components and event-driven nature make it suitable for microservices, but you'll need to handle inter-service communication and event streaming separately, as it doesn't include built-in messaging.

How to persist events in Broadway?

Broadway doesn't include a default event store; you need to implement or use a compatible persistence layer, such as a database or message queue, by extending its interfaces or using community packages.

Can Broadway handle real-time updates?

While Broadway supports event sourcing, real-time features like WebSockets are not built-in. You'll need to integrate additional libraries or custom code to push events to clients in real-time.

What are the performance implications of using Broadway?

Event sourcing can add overhead due to event storage and replay, but Broadway's lightweight design minimizes this. Performance depends on your implementation, such as event store choice and aggregate design.

Open-Awesome

Broadway

MITPHP2.5.0

Infrastructure and testing helpers for building CQRS and event-sourced applications in PHP.

Visit Website GitHub

1.5k stars171 forks0 contributors

What is Broadway?

Broadway is a PHP framework that provides infrastructure and testing helpers for building applications using CQRS (Command Query Responsibility Segregation) and event sourcing patterns. It offers loosely coupled components to implement these architectures, helping developers manage complex domain logic with clear separation of commands, queries, and events.

Target Audience

PHP developers building scalable, maintainable applications with complex business logic, particularly those adopting domain-driven design, CQRS, or event sourcing patterns.

Value Proposition

Developers choose Broadway because it provides essential CQRS/ES infrastructure without getting in the way, offers decoupled components for flexibility, and includes dedicated testing helpers to ensure reliability in event-sourced systems.

Overview

Infrastructure and testing helpers for creating CQRS and event sourced applications.

Use Cases

Best For

Implementing event-sourced aggregates in PHP applications
Building scalable systems with CQRS architecture
Testing complex domain logic in event-driven systems
Adopting domain-driven design with event sourcing
Creating maintainable applications with clear command/query separation
Developing applications that require audit trails and event replay

Not Ideal For

Projects requiring simple CRUD operations without complex business logic
Teams needing a full-stack framework with built-in HTTP handling and templating
Applications where real-time event processing is a primary requirement
Developers who prefer convention-over-configuration frameworks with minimal setup

Pros & Cons

Pros

Decoupled Component Design

Components are loosely coupled, allowing independent use or full CQRS/ES integration, as highlighted in the README's emphasis on flexibility.

Specialized Testing Tools

Includes helpers for testing event-sourced aggregates and command handlers, making it easier to ensure domain logic correctness in complex systems.

Non-Intrusive Infrastructure

Designed to stay out of the way, providing necessary CQRS/ES building blocks without imposing rigid constraints, inspired by frameworks like Axon.

Proven Pattern Inspiration

Draws from established CQRS frameworks like Axon Framework and Ncqrs, ensuring well-architected components based on industry best practices.

Cons

Additional Setup Required

Lacks built-in persistence for event stores and read models, requiring developers to integrate external solutions, which adds complexity.

Complex Pattern Dependency

Requires thorough understanding of CQRS and event sourcing concepts, which can be a barrier for teams new to these architectural patterns.

Ecosystem Limitations

As a niche framework, it has a smaller community and fewer third-party integrations compared to mainstream PHP frameworks like Laravel or Symfony.

Documentation Fragmentation

Detailed documentation is hosted on a separate site (broadway.github.io), which might not be as accessible or regularly updated as inline documentation.

Frequently Asked Questions

Related Projects

Swoole

🚀 Coroutine-based concurrency library for PHP

Stars18,900

Forks3,148

Last commit3 days ago

Workerman

An asynchronous event driven PHP socket framework. Supports HTTP, Websocket, SSL and other custom protocols.

Stars11,552

Forks2,254

Last commit21 days ago

ReactPHP

Event-driven, non-blocking I/O with PHP.

Stars9,089

Forks714

Last commit1 year ago

Ratchet

Asynchronous WebSocket server

Stars6,436

Forks791

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub