Weave Code
P Service Bus Symfony Bundle Laravel Package
gdx/p-service-bus-symfony-bundle
GDX Service Bus Symfony Bundle integrates a message bus into Symfony apps. Wire commands, queries, and events to handlers with dependency-injection support, middleware pipelines, handler autoconfiguration, and clean YAML/PHP configuration for scalable message-driven PHP applications.
PServiceBus
Frequently asked questions about P Service Bus Symfony Bundle
- Can I use gdx/p-service-bus-symfony-bundle in a Laravel application?
- Not directly. The package is a Symfony bundle: its value comes from config/bundles.php registration, a Bundle subclass, a DI extension with a config tree, and compiler passes that tag handlers and middleware into Symfony's ContainerBuilder. Laravel has no equivalent bundle model, so those artifacts are inert there. The only viable path is evaluating the underlying gdx/p-service-bus core library and wrapping it in your own service provider if it proves framework-agnostic.
- What does gdx/p-service-bus-symfony-bundle actually do?
- It integrates the GDX Service Bus into Symfony applications by wiring command, query, and event buses into the dependency injection container. Handlers and middleware are defined as ordinary services, and you dispatch messages through autowired bus interfaces. It also provides automatic handler registration via service tags or attributes, configurable buses per message type, and YAML or PHP configuration for message-driven applications.
- How do I install and configure the bundle?
- Install it with Composer using composer require gdx/p-service-bus-symfony-bundle, then register the bundle in config/bundles.php for the environments you need. Configuration typically lives in config/packages/ and lets you declare buses, handler discovery, and middleware pipelines. Note that this is a Symfony installation flow only; no Laravel package discovery or service provider is shipped with it.
- How are command, query, and event handlers registered?
- Handlers are registered automatically, either by tagging their services or by using PHP attributes, and a compiler pass collects them into the relevant bus at container build time. Because handlers are regular Symfony services, they receive full constructor autowiring for repositories, loggers, and other dependencies. This keeps domain code decoupled from the bus infrastructure.
- Does the bundle support middleware pipelines?
- Yes. Middleware can be registered as services and composed into per-bus pipelines, which makes it suitable for cross-cutting concerns such as logging, validation, transactions, or metrics. Ordering is controlled through configuration, so concerns like transaction wrapping can be placed deterministically around handler execution.
- Is the gdx/p-service-bus core library framework-agnostic enough to use with Laravel's container?
- That is not documented in the available metadata and should be the first thing you verify. A Laravel adapter is only realistic if the core exposes clean contracts for bus, handler resolution, transport, and serialization against PSR-11 or PSR-14 without hard-depending on symfony/framework-bundle or Symfony's ContainerBuilder. If the core assumes Symfony tagged services or compile-time wiring, integration cost rises sharply and the value proposition weakens.
- Which PHP and Symfony versions does it support, and will it conflict with Laravel's pinned symfony components?
- The PHP and symfony/* constraints are not stated in the package overview, so check composer.json before committing to anything. This matters for Laravel because Laravel transitively pins several symfony/* components, and a conflicting Symfony major version can produce a Composer deadlock. Run composer why-not against your target Laravel and PHP versions as an early spike.
- What transports does it support, and does it handle retries, dead-letter queues, or an outbox pattern?
- Supported transports, serialization format, retry policy, dead-letter handling, and transactional outbox support are not described in the available documentation. Treat all of them as unknown until you read the core library documentation and source. For production use you need a confirmed round-trip with retries and a dead-letter path, plus a plan for messages whose class changes while others are still in flight.
- How do I test handlers and bus wiring with this package?
- Handlers are plain services, so unit testing is straightforward: instantiate the handler with mocked dependencies and pass it a message. Integration tests should dispatch a message through the configured bus inside the container and assert that the handler ran and that middleware behaved as expected. If you build a Laravel adapter, use an in-memory transport and Laravel's container to verify handler resolution end to end.
- Is gdx/p-service-bus-symfony-bundle actively maintained and production-ready?
- Community validation is essentially absent: zero stars, zero dependents, and no public bug reports, with the maintainer's release cadence and support commitment unverified. Treat it as an evaluation spike rather than a commitment, and keep the bus behind your own interfaces so it can be swapped. For Laravel projects, the native command bus and queue dispatch, Symfony Messenger, or established CQRS libraries are usually safer defaults.
Weaver
How can I help you explore Laravel packages today?