Chapters

48 Chapters | 5:05:05 |

01

Instalar el Messenger

6:15
02

Mensaje, Manejador y el Bus

8:36
03

Haciendo el trabajo en el controlador

6:32
04

Mensaje, manejador y depuración:messenger

5:51
05

Transporte: Haz el trabajo después (asíncrono)

7:33
06

Comando del trabajador

5:34
07

Problemas con las entidades en los mensajes

4:53
08

Pasar Ids de entidad dentro de los mensajes

8:00
09

¿Despachar un mensaje dentro de un manejador?

5:30
10

Fallos parciales del manejador y enrutamiento avanzado

4:35
11

Sobres y sellos

6:23
12

Reintentar en caso de fallo

5:11
13

Retraso en el reintento y estrategia de reintento

4:40
14

El transporte de fallos

5:37
15

Investigar y reintentar mensajes fallidos

5:41
16

Middleware

5:59
17

Seguimiento de los mensajes con el middleware y un sello

5:31
18

Configuración del canal de registro y autoconexión

5:26
19

Registro del ciclo de vida de los mensajes del middleware

7:47
20

Transportes de alta prioridad

5:40
21

Manejar la sincronización de mensajes mientras se desarrolla

5:54
22

Prueba funcional del punto final de carga

9:22
23

Probando con el transporte "en memoria

5:26
24

Despliegue y supervisión

9:08
25

Matar a los trabajadores antes de tiempo y en el despliegue

5:55
26

Eventos y bus de eventos

5:22
27

Creación y manejo de eventos

7:55
28

Despacho del evento y sin manejadores

7:06
29

Messenger vs EventDispatcher

3:18
30

Middleware de transacción y validación de Doctrine

5:58
31

Organización del bus de eventos y comandos

7:23
32

Autobús turístico

8:47
33

Configuración avanzada del manipulador: Suscriptores del Manejador

7:58
34

Envío de manejadores a diferentes transportes: from_transport

3:21
35

AMQP con RabbitMQ

7:22
36

Aspectos internos de AMQP: Intercambios y colas

8:10
37

Intercambio de prioridades AMQP

7:15
38

Retraso en AMQP: intercambio de letra muerta

7:23
39

Intercambio de Claves de Enrutamiento y Vinculación

6:38
40

Clave de enrutamiento AMQP dinámica (AmqpStamp)

7:50
41

Serializar mensajes como JSON

6:41
42

JSON, cabeceras de mensajes y opciones del serializador

3:15
43

Configuración de los mensajes de un sistema externo

6:01
44

Transporte para consumir mensajes externos

5:51
45

Serializador de transporte personalizado

6:33
46

El ciclo de vida de un mensaje y sus sellos

8:16
47

Fallo Gracioso en el Serializador de Transporte

4:47
48

Asignación de mensajes a clases en un serializador de transporte

4:56

> Symfony 5 > ¡Messenger! Encola el trabajo para Despues

Buy Access to Course

19.

Registro del ciclo de vida de los mensajes del middleware

|

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

7 Comments

Sort By

Login or Register to join the conversation

ahmedbhs 5 years ago

Does there a way to use that unique id to remove a failed message from failure transport for example ?

|

MolloKhan SFCASTS ahmedbhs 5 years ago edited

Hey ahmedbhs

If you have a message hanging in the failed queue, then, you can use Messenger's commands to investigate more about it. There are these 3 commands you can play with and decide what to do with such a message
messenger:failed:remove
messenger:failed:retry
messenger:failed:show

Cheers!

-1 |

kwolniak 6 years ago edited

Hi

if i have routing like this:
`
routing:

'App\Events\SomeEvent': [one, two]

`

Is it possible somehow, (depend on some logic in code) to send message only to "<b>two</b>" transport?
I'm using AWS SQS.

|

MolloKhan SFCASTS kwolniak 6 years ago edited

Hey kwolniak

There is a way to do that, a bit confusing but possible. Here you can learn how https://symfonycasts.com/sc...

Cheers!

|

kwolniak MolloKhan 6 years ago

Thanks, I know this "from_transport" thing, but it's not what I need.
When I declare routing like above, SomeEvent message is sent automaticaly to one and two transport. And the same message appear in my case on one and two queue and in most cases it's OK.
But sometimes I want change it on the runtime in the code (for example somehow in middleware or before dispatch) and sent it only to one transport so message will appear only in one queue.
I have found that it should be possible with ampq and routing key but is it possible when I'm using enqueue/sqs?

|

weaverryan SFCASTS kwolniak 6 years ago edited

Hey kwolniak!

This is currently a shortcoming with Messenger - and probably the one that bothers me the most! Routing is super static - there is no way to hook in at runtime to modify this. I think there should be, but it's not there yet. So, you have 2 options:

1) Do fanciness with routing key and amqp (or something similar in sqs... if there is such a mechanism). This is basically you going outside of the system to get what you want ;).

2) Create 2 different classes: one that routes to both transports and another that routes to only one.

SUPER not ideal, but that's the state of things. Hmm, or you could do something totally nuts and "decorate" (with Symfony service decoration) the messenger.senders_locator service (which is this class https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Messenger/Transport/Sender/SendersLocator.php) and do some custom logic there. That is the "I'm taking full control" hammer solution to the problem - but because there isn't such a nice solution yet, I won't be disappointed if you do it ;).

Cheers!

1 |

kwolniak weaverryan 6 years ago

Thank you very much for the comprehensive answer!
For now I decided on two separate events and two separate transports, and before dispatch I do some logic.

Thanks anyway :)

|

Este tutorial está construido con Symfony 4.3, pero funcionará bien en Symfony 4.4 o 5.

Symfony 4.3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // v1.8.0
        "doctrine/doctrine-bundle": "^1.6.10", // 1.11.2
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // v2.0.0
        "doctrine/orm": "^2.5.11", // v2.6.3
        "intervention/image": "^2.4", // 2.4.2
        "league/flysystem-bundle": "^1.0", // 1.1.0
        "phpdocumentor/reflection-docblock": "^3.0|^4.0", // 4.3.1
        "sensio/framework-extra-bundle": "^5.3", // v5.3.1
        "symfony/console": "4.3.*", // v4.3.2
        "symfony/dotenv": "4.3.*", // v4.3.2
        "symfony/flex": "^1.9", // v1.21.6
        "symfony/framework-bundle": "4.3.*", // v4.3.2
        "symfony/messenger": "4.3.*", // v4.3.4
        "symfony/property-access": "4.3.*", // v4.3.2
        "symfony/property-info": "4.3.*", // v4.3.2
        "symfony/serializer": "4.3.*", // v4.3.2
        "symfony/validator": "4.3.*", // v4.3.2
        "symfony/webpack-encore-bundle": "^1.5", // v1.6.2
        "symfony/yaml": "4.3.*" // v4.3.2
    },
    "require-dev": {
        "easycorp/easy-log-handler": "^1.0.7", // v1.0.7
        "symfony/debug-bundle": "4.3.*", // v4.3.2
        "symfony/maker-bundle": "^1.0", // v1.12.0
        "symfony/monolog-bundle": "^3.0", // v3.4.0
        "symfony/stopwatch": "4.3.*", // v4.3.2
        "symfony/twig-bundle": "4.3.*", // v4.3.2
        "symfony/var-dumper": "4.3.*", // v4.3.2
        "symfony/web-profiler-bundle": "4.3.*" // v4.3.2
    }
}

Previous Chapter

Next Chapter