php-service-bus/service-bus

PHP Service Bus (publish-subscribe pattern) implementation

service-bus's Issues

Implementation of mutexes

Now, with several competitive messages, the sagas do not work very much as expected. It is necessary to implement mutexes. By default, local mutexes (in memory) should be used. For multiple processes, Redis will be implemented.

Are you planning implement query messages?

I like your project. Are you planning implement query messages?

AggregateId is not marked as immutable

Is it intended - allow to add side effects/mutations in descendants?

https://github.com/php-service-bus/event-sourcing/blob/v4.2.0/src/AggregateId.php

demo application start up not working

Hi There,

I am trying to setup demo application. Docker compose is not able to start following container
service-bus-uber-consumer
When I looked into docker-compose.yml file the following line
https://github.com/php-service-bus/demo/blob/d53b8cdb151fb7a7da29fa35200bdae91994697d/docker-compose.yaml#L45
But /tools/boot does not exist.

Support swoole?

Can we use this package on Swoole, It seems Swoole is more popular than APM.

Redis transport implementation

Implement transport based on Redis pub\sub.
amphp/redis will be used as a library for working with Redis.

Transactional integrity.

If I have a database operation in the message handler and in that handler I dispatch new messages, is there a guaranty those messages will be dispatch after the database transaction is completed?
In the NServiceBus they first save all messages in the database and only after try to send messages to a message system (for example, RabbitMQ). Those give guaranty message will be dispatch only if massing handler succeeds successfully (No error occur).
Does this implementation do the same thing?

Work with Azure Service Bus?

This package works with azure service bus? Have support for azure connector?