Download the PHP package octo-php/symfony-messenger without Composer
On this page you can find all versions of the php package octo-php/symfony-messenger. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download octo-php/symfony-messenger
More information about octo-php/symfony-messenger
Files in octo-php/symfony-messenger
Package symfony-messenger
Short Description Symfony Messenger transport for the Async PHP Platform — in-process message passing via bounded OpenSwoole channels with backpressure.
License MIT
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 symfony-messenger
octo-php/symfony-messenger
Transport Symfony Messenger in-process pour la plateforme async PHP — message passing via channels OpenSwoole bornés avec backpressure.
Installation
Configuration
DSN
Variables d'environnement
| Variable | Type | Défaut | Description |
|---|---|---|---|
OCTOP_SYMFONY_MESSENGER_CHANNEL_CAPACITY |
int | 100 |
Capacité du channel borné (backpressure) |
OCTOP_SYMFONY_MESSENGER_CONSUMERS |
int | 1 |
Nombre de coroutines consommatrices par worker |
OCTOP_SYMFONY_MESSENGER_SEND_TIMEOUT |
float (s) | 5.0 |
Timeout d'envoi quand le channel est plein |
Via le bundle
Fonctionnement
Le transport utilise un channel OpenSwoole borné pour le message passing in-process :
send(): push le message dans le channel. Si le channel est plein, la coroutine yield (backpressure) jusqu'à ce qu'un espace soit disponible ou que le timeout soit atteint.get(): pop un message du channel avec un poll timeout de 1s.ack(): no-op (in-process, pas de broker externe).reject(): log warning.
Les consumers sont spawnés au boot du worker via structured concurrency (TaskGroup) et annulés proprement au shutdown (pas de coroutines zombies).
Métriques
| Métrique | Type | Description |
|---|---|---|
messenger_messages_sent_total |
counter | Messages envoyés |
messenger_messages_consumed_total |
counter | Messages consommés |
messenger_channel_size |
gauge | Taille courante du channel |
Limitations
Transport in-process uniquement
Ce transport est non distribué et non durable :
- Les messages sont stockés en mémoire dans le channel OpenSwoole du worker
- Le channel est isolé par worker : les messages ne sont pas partagés entre workers
- Les messages non consommés au moment du restart du worker sont perdus
Cas d'usage adaptés
- Fire-and-forget (notifications, logs asynchrones)
- Background jobs légers (envoi d'emails, cache warming)
- Traitement asynchrone intra-requête
Cas d'usage non adaptés
Pour le messaging durable, distribué ou critique, utiliser les transports externes standard Symfony :
- AMQP (RabbitMQ)
- Redis
- Doctrine
Retry et failure transport
Les mécanismes standard de retry et failure transport de Symfony Messenger s'appliquent normalement :
Pour les messages critiques, configurez un failure transport durable (Doctrine, Redis) afin de ne pas perdre les messages en cas de restart.
Licence
MIT
All versions of symfony-messenger with dependencies
octo-php/runtime-pack Version ^0.1
octo-php/symfony-bridge Version ^0.1
symfony/messenger Version ^6.4|^7.0