Download the PHP package wallsfantasy/service-bus-laravel-package without Composer
On this page you can find all versions of the php package wallsfantasy/service-bus-laravel-package. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wallsfantasy/service-bus-laravel-package
More information about wallsfantasy/service-bus-laravel-package
Files in wallsfantasy/service-bus-laravel-package
Package service-bus-laravel-package
Short Description A package for leveraging the Prooph Service Bus in a Laravel project
License BSD-3-Clause
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package service-bus-laravel-package
Laravel Service Bus Package
This package supports the use of the prooph service buses inside of a Laravel application.
Features
- [x] Support default buses that are bound to the classes
- [x] Support unlimited named buses
- [x] Add loggers to all buses
- [x] Automatically resolve handlers
- [x] Collect profiling data in debug mode
- [x] Async switch
Installation
composer require camuthig/service-bus-laravel-package
Setup
Publish the Config
php artisan vendor:publish
Include the Provider
The package will automatically be discovered by Laravel when installed, no changes to include the service provider are needed.
Usage
Getting Default Buses
The default instance of each bus type can be retrieved in two ways:
Each bus type (command, event and query) includes both a singleton interface as well as a facade.
ServiceBusManager
This package also supports having more than one of each bus type. To leverage a
non-default bus, you will want to use the ServiceBusManager. The manager gives
you access to all of the buses by name.
The service manager can be retrieved in three ways:
Configuration
The buses can be configured using the service_bus.php configuration file. Each
type of bus will have it's own list of of named buses with the following options:
- message_factory The service ID or class name of the message factory to use with the bus. The default is the prooph FQCNMessageFactory if this key is not provided.
- action_event_emitter The service ID or class name of the message factory to use with the bus. The default is the prooph ProophActionEventEmitter if this key is not provided.
- plugins A list of service IDs or class names of plugins to add to the the bus.
- router The configuration for the bus' router plugin. See details below
Router configuration
The router for each bus can be configured with:
- type The class name of a
MessageBusRouterPluginto use for this bus. It is expected that the constructor for the router should accept an array of route mappings. See the proophCommandRouter,EventRouter, andQueryRouterclasses for examples. This will default to the appropriate prooph router based on the type of the bus if not provided. - async_switch The service ID or class name of an
AsyncSwitchMessageRouterto add to the bus. If this value is not provided, no switch will be included on the bus. - routes A list of route mappings
- Command and query routing: Each entry in the list of routes is a "message name" to "message processor" (either a command handler or query finder).
- Event routing: Each entry in the list of routes is a "message name" to "list of listeners".
