All Projects → php-service-bus → Service Bus

php-service-bus / Service Bus

Licence: mit
PHP Service Bus (publish-subscribe pattern) implementation

Projects that are alternatives of or similar to Service Bus

Event Store Client
PHP 7.4 Event Store Client Implementation
Stars: ✭ 93 (-67.93%)
Mutual labels:  async, event-sourcing
Process
An async process dispatcher for Amp.
Stars: ✭ 119 (-58.97%)
Mutual labels:  async, amphp
Acme
Async ACME library written in PHP based on the Amp concurrency framework.
Stars: ✭ 102 (-64.83%)
Mutual labels:  async, amphp
Sync
Synchronization primitives for PHP based on Amp.
Stars: ✭ 67 (-76.9%)
Mutual labels:  async, amphp
Mysql
Async MySQL client for PHP based on Amp.
Stars: ✭ 235 (-18.97%)
Mutual labels:  async, amphp
Dns
Async DNS resolution for PHP based on Amp.
Stars: ✭ 82 (-71.72%)
Mutual labels:  async, amphp
Madelineproto
Async PHP client/server API for the telegram MTProto protocol
Stars: ✭ 1,776 (+512.41%)
Mutual labels:  async, amphp
Riker
Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.
Stars: ✭ 745 (+156.9%)
Mutual labels:  async, event-sourcing
Byte Stream
A non-blocking stream abstraction for PHP based on Amp.
Stars: ✭ 208 (-28.28%)
Mutual labels:  async, amphp
Message Bus
Go simple async message bus
Stars: ✭ 166 (-42.76%)
Mutual labels:  async, event-sourcing
Http Server
A non-blocking HTTP application server for PHP based on Amp.
Stars: ✭ 1,122 (+286.9%)
Mutual labels:  async, amphp
muon-java
Muon Core for the JVM. APIs and Microservices taken to the next level
Stars: ✭ 18 (-93.79%)
Mutual labels:  messaging, event-sourcing
Postgres
Async Postgres client for PHP based on Amp.
Stars: ✭ 56 (-80.69%)
Mutual labels:  async, amphp
Websocket Client
Async WebSocket client for PHP based on Amp.
Stars: ✭ 83 (-71.38%)
Mutual labels:  async, amphp
Demo Chat
A small demo chat based on Aerys.
Stars: ✭ 18 (-93.79%)
Mutual labels:  async, amphp
Redis
Async Redis Client for PHP based on Amp.
Stars: ✭ 107 (-63.1%)
Mutual labels:  async, amphp
Lapin
AMQP client library in Rust, with a clean, futures based API
Stars: ✭ 497 (+71.38%)
Mutual labels:  async, messaging
Http Client
Async HTTP/1.1+2 client for PHP based on Amp.
Stars: ✭ 553 (+90.69%)
Mutual labels:  async, amphp
Socket
Non-blocking socket and TLS functionality for PHP based on Amp.
Stars: ✭ 122 (-57.93%)
Mutual labels:  async, amphp
microservice framework version 6
A Java framework to support applications utilising CQRS and Event Sourcing architectures
Stars: ✭ 25 (-91.38%)
Mutual labels:  messaging, event-sourcing

Packagist Packagist Continuous Integration codecov Shepherd Latest Stable Version License Financial Contributors on Open Collective

Introduction

A concurrency (based on Amp) framework, that lets you implement an asynchronous messaging, a transparent workflow and control of long-lived business transactions by means of the Saga pattern. It implements the message based architecture and it includes the following patterns: Saga, Publish\Subscribe, Message Bus.

Main Features

  • Сooperative multitasking
  • Asynchronous messaging (Publish\Subscribe pattern implementation)
  • Event-driven architecture
  • Distribution (messages can be handled by different applications)
    • Subscribers can be implemented on any programming language
  • High performance
  • Orchestration of long-lived business transactions (for example, a checkout) with the help of Saga Pattern
  • Full history of aggregate changes (EventSourcing)

See it in action

Jump into our Quick Start and build your first distributed solution in just 15 minutes.

Documentation

Documentation can be found in the .documentation directory

Requirements

  • PHP >=8.0
  • RabbitMQ/Redis/Nsq
  • PostgreSQL

Contributions are welcome! Please read CONTRIBUTING for details.

Communication Channels

You can find help and discussion in the following places:

Contributing

Contributions are welcome! Please read CONTRIBUTING for details.

License

The MIT License (MIT). Please see LICENSE for more information.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].