Download the PHP package nilportugues/messagebus without Composer

Message Bus

Implementation for the CommandBus, the QueryBus and the EventBus in PHP 7 and using PSR-11.

• Installation
• Introduction
• What is a Message Bus?
• What are its benefits?
• 1. CommandBus
  • 1.1 - Usage
    • 1.1.1 - Create a Command
    • 1.1.2 - Create a CommandHandler
    • 1.1.3 - Register the CommandHandler
    • 1.1.4 - Setting up the CommandBus
    • 1.1.5 - Registering the remaining CommandBus classes
    • 1.1.6 - Running the CommandBus
  • 1.2 - Predefined Middlewares
  • 1.3 - Custom Middlewares
• 2. QueryBus
  • 2.1 - Usage
    • 2.1.1 - Create a Query
    • 2.1.2 - Create a QueryHandler
    • 2.1.3 - Create a QueryResponse
    • 2.1.4 - Register the QueryHandler
    • 2.1.5 - Setting up the QueryBusMiddleware
    • 2.1.6 - Registering the remaining QueryBus classes
    • 2.1.7 - Running the QueryBus
  • 2.2 - Predefined Middlewares
  • 2.3 - Custom Middlewares
• 3. EventBus
  • 3.1 - Usage
    • 3.1.1 - Create an Event
    • 3.1.2 - Create an EventHandler
    • 3.1.3 - (Optional) Set the EventHandler's Priority
    • 3.1.4 - Register the EventHandler
    • 3.1.5 - Setting up the EventBusMiddleware
    • 3.1.6 - Registering the remaining EventBus classes
    • 3.1.7 - Running the EventBus
    • 3.1.8 - (Optional) Running the EventBus as a Queue
  • 3.2 - Predefined Middlewares
  • 3.3 - Custom Middlewares
• 4 - Serializers
  • 4.1 - NilPortugues\MessageBus\Serializer\NativeSerializer
  • 4.2 - NilPortugues\MessageBus\Serializer\JsonSerializer
  • 4.3 - NilPortugues\MessageBus\Serializer\JsonObjectSerializer
• Contribute
• Support
• Authors
• License

Installation

Use Composer to install the package:

Introduction

The idea of a message bus is that you create message objects that represent what you want your application to do. Then, you toss it into the bus and the bus makes sure that the message object gets to where it needs to go.

Easy right? Keep reading!

What is a Message Bus?

A Message Bus is a pipe of Messages. This implementation takes care of 3 types of messages, Commands, Queries and Events. While all look similar at first, their intent is different.

• Command: its intent is about expressing an order to the system and modifies its current state. User expects no response.
• Event: its intent is to express something that has already happened in the system, and record it. User expects no response.
• Query: its intent is about expressing a question to the system. User expects a response.

From this classification, one can spot that Command and Events can work together very well.

What are its benefits?

Given the nature of the message, implementing an interface, you may write behaviours that wrap the message to log, process or modify the response using the Decorator pattern. These are called Middleware.

For instance:

• Implementing task-based user-interfaces you can map concepts to Commands, Queries and Events easily.
• It allows you to easily write a logging system to know what's going, whether its a Command, a Query or an Event. It's possible.

To wrap-up, its benefits are:

• Encourages separation of concerns.
• Encourages single responsibility design.

1. CommandBus

1.1 - Usage

1.1.1 - Create a Command

1.1.2 - Create a CommandHandler

The Command Handler must implement the CommandHandler interface and implement the __invoke method.

For instance:

1.1.3 - Register the CommandHandler

I'm assuming you're using some kind Service Container. Now it's time to register your CommandHandler.

For instance, in a Psr\Container compliant Service Container, we can do this as follows:

1.1.4 - Setting up the CommandBus

The Command Bus Middleware requires two classes to be injected. First one is the command translator, and second one the handler resolver.

CommandTranslator

Classes implementing this interface will provide the FQN for the Handler class given a Command.

This package provides an implementation, NilPortugues\MessageBus\CommandBus\Translator\AppendStrategy which basically appends the word Handler to the provided Command class.

For custom strategies, you may write your own implementing the NilPortugues\MessageBus\CommandBus\Contracts\CommandTranslator interface.

CommandHandlerResolver

Classes implementing this interface will be resolving the class for the instance required based on the output of the CommandTranslator used.

This package provides an implementation, NilPortugues\MessageBus\CommandBus\Resolver\PsrContainerResolver, that expects any Service Container implementing the Psr\Container interface.

For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: NilPortugues\MessageBus\CommandBus\Resolver\SymfonyContainerResolver. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.

1.1.5 - Registering the remaining CommandBus classes

The minimum set up to get the Command Bus working is:

If for instance, we want to log everything happening in the Command Bus, we'll add to the middleware list the logger middleware. This will wrap the Command Bus, being able to log before and after it ran, and if there was an error.

1.1.6 - Running the CommandBus

Finally, to make use of the CommandBus, all you need to do is run this code:

1.2 - Predefined Middlewares

TransactionalCommandBusMiddleware

• Class: NilPortugues\MessageBus\CommandBus\TransactionalCommandBusMiddleware
• Class construct method expects a PDO connection. It will wrap all the underlying middleware calls with beginTransaction-commit and rollback if any kind of exception is thrown.

LoggerQueryBusMiddleware

• Class: NilPortugues\MessageBus\CommandBus\LoggerCommandBusMiddleware
• Class construct method expects a PSR3 Logger implementation.

1.3 - Custom Middlewares

In order to write custom middleware a new class implementing the NilPortugues\MessageBus\CommandBus\Contracts\CommandBusMiddleware interface is required.

2. QueryBus

2.1 - Usage

2.1.1 - Create a Query

2.1.2 - Create a QueryHandler

The Query Handler must implement the QueryHandler interface and implement the __invoke method.

For instance:

2.1.3 - Create a QueryResponse

Response queries are generic responses.

If you take into account section 2.1.2, you'll see the UserQueryResponse has a $user injected into the constructor. This has been done in order to reuse the QueryResponse in other scenarios such as fetching an updated user.

2.1.4 - Register the QueryHandler

I'm assuming you're using some kind Service Container. Now it's time to register your QueryHandler.

For instance, in a Psr\Container compliant Service Container, we can do this as follows:

2.1.5 - Setting up the QueryBusMiddleware

The Query Bus Middleware requires two classes to be injected. First one is the query translator, and second one the handler resolver.

QueryTranslator

Classes implementing this interface will provide the FQN for the Handler class given a Query.

This package provides an implementation, NilPortugues\MessageBus\QueryBus\Translator\AppendStrategy which basically appends the word Handler to the provided Query class.

For custom strategies, you may write your own implementing the NilPortugues\MessageBus\QueryBus\Contracts\QueryTranslator interface.

QueryHandlerResolver

Classes implementing this interface will be resolving the class for the instance required based on the output of the QueryTranslator used.

This package provides an implementation, NilPortugues\MessageBus\QueryBus\Resolver\PsrContainerResolver, that expects any Service Container implementing the Psr\Container interface.

For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: NilPortugues\MessageBus\QueryBus\Resolver\SymfonyContainerResolver. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.

2.1.5 - Registering the remaining QueryBus classes

The minimum set up to get the Query Bus working is:

If for instance, we want to log everything happening in the Query Bus, we'll add to the middleware list the logger middleware. This will wrap the Query Bus, being able to log before and after it ran, and if there was an error.

2.1.6 - Running the QueryBus

Finally, to make use of the QueryBus, all you need to do is run this code:

2.2 - Predefined Middlewares

CacheQueryBusMiddleware

• Class: NilPortugues\MessageBus\QueryBus\CacheQueryBusMiddleware
• Class construct method expects a Serializer (see below), a PSR6 Caching implementation and queue name.

LoggerQueryBusMiddleware

• Class: NilPortugues\MessageBus\QueryBus\LoggerQueryBusMiddleware
• Class construct method expects a PSR3 Logger implementation.

2.3 - Custom Middlewares

In order to write custom middleware a new class implementing the NilPortugues\MessageBus\QueryBus\Contracts\QueryBusMiddleware interface is required.

3. EventBus

3.1 - Usage

3.1.1 - Create an Event

We'll be creating an Event. Due to the nature of events, an event may be mapped to one or more Event Handlers.

3.1.2 - Create an EventHandler

To illustrate the power of eventing, we'll map the previous event UserRegistered to two EventHandlers.

First Event Handler

First event handler we'll create assumes we've got an email service to send a welcome email.

Second Event Handler

Second event handler we'll create the relationships in our database for user friends and user credits.

3.1.3 - (Optional) Set the EventHandler's Priority

Sometimes you want or must make sure an action precedes another one.

By default, all events have a priority, this being set by the EventHandlerPriority::LOW_PRIORITY constant value.

To implement your priority order in your classes implement the EventHandler interface, must implement another interface, the EventHandlerPriority.

For instance, if we would like SendWelcomeEmailHandler to happen after SetupUserAccountHandler, we should give the first less priority, or the latter more.

SetupUserAccountHandler should go first when dispatching event UserRegistered

SendWelcomeEmailHandler should go second when dispatching event UserRegistered

Notice how a good idea is to set up relative ordering by subtracting to the MAX_PRIORITY order.

3.1.4 - Register the EventHandler

I'm assuming you're using some kind Service Container. Now it's time to register your Event Handlers.

For instance, in a Psr\Container compliant Service Container, we can do this as follows:

3.1.5 - Setting up the EventBusMiddleware

The Event Bus Middleware requires two classes to be injected. First one is the Event translator, and second one the handler resolver.

EventTranslator

Takes care of registering the EventHandlers subscribed to an Event.

Its implementation can be found at: NilPortugues\MessageBus\EventBus\Translator\EventFullyQualifiedClassNameStrategy.

EventHandlerResolver

Classes implementing this interface will be resolving the class for the instance required based on the output of the EventTranslator used.

This package provides an implementation, NilPortugues\MessageBus\EventBus\Resolver\PsrContainerResolver, that expects any Service Container implementing the Psr\Container interface.

For Symfony 2 and 3 framework users up to version 3.2, you should use Symfony Container: NilPortugues\MessageBus\EventBus\Resolver\SymfonyContainerResolver. For Symfony 3.3 and up use the PSR-11 ContainerResolver class.

3.1.6 - Registering the remaining EventBus classes

The minimum set up to get the Event Bus working is:

If for instance, we want to log everything happening in the Event Bus, we'll add to the middleware list the logger middleware. This will wrap the Event Bus, being able to log before and after it ran, and if there was an error.

3.1.7 - Running the EventBus

Finally, to make use of the EventBus, all you need to do is run this code:

3.1.8 - (Optional) Running the EventBus as a Queue

Save your users time and load your pages faster! Go asynchronous using a queue.

To do so, you'll have to require an additional package: EventBus Queue. This extension can be downloaded using composer:

Documentation and installation guide can be found in its repository.

3.2 - Predefined Middlewares

TransactionalEventBusMiddleware

• Class: NilPortugues\MessageBus\EventBus\TransactionalEventBusMiddleware
• Class construct method expects a PDO connection. It will wrap all the underlying middleware calls with beginTransaction-commit and rollback if any kind of exception is thrown.

LoggerEventBusMiddleware

• Class: NilPortugues\MessageBus\EventBus\LoggerEventBusMiddleware
• Class construct method expects a PSR3 Logger implementation.

ProducerEventBusMiddleware

• Class: NilPortugues\MessageBus\EventBusQueue\ProducerEventBusMiddleware
• Adds events to an Event Queue. Required running composer require nilportugues/eventbus-queue first.

3.3 - Custom Middlewares

In order to write custom middleware a new class implementing the NilPortugues\MessageBus\EventBus\Contracts\EventBusMiddleware interface is required.

4 - Serializers

Serializers are to be used mainly all the <Name>ProducerEventBusMiddleware classes. You may also find this in Cache classes.

Choose one or another depending on your needs.

4.1 - NilPortugues\MessageBus\Serializer\NativeSerializer

For caching, this is the best option.

In the EventBus use this if your Consumer is written in PHP and will share the same code base as the object serialized.

• Pros: Fastest serialization possible.
• Cons: Consumer must be written in PHP and classes must be available or unserialize will fail.

4.2 - NilPortugues\MessageBus\Serializer\JsonSerializer

Not recommended for caching.

In the EventBus use this if your Consumer is written in PHP but your consumers may be written in many languages.

• Pros: If consumer is PHP, the data will be restored and if sharing the same code base as the object serialized, an object can be obtained on unserialize. If not, you may be able to fetch data manually as regular JSON.
• Cons : If fetching data from the data-store as JSON it will hold references to the PHP data-structure, but does not interfere consuming data.

4.3 - NilPortugues\MessageBus\Serializer\JsonObjectSerializer

Doesn't work for caching.

In the EventBus use this if your Consumer is written in PHP but you're not consuming data currently.

• Pros: JSON can be reused to consume this data in the future as its supported everywhere.
• Cons: You'll have to write your consumer to read the JSON structure.

Contribute

Contributions to the package are always welcome!

• Report any bugs or issues you find on the issue tracker.
• You can grab the source code at the package's Git repository.

Support

Get in touch with me using one of the following means:

• Emailing me at [email protected]
• Opening an Issue

Authors

• Nil Portugués Calderó
• The Community Contributors

License

The code base is licensed under the MIT license.