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

32.

Autobús turístico

|

|

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

6 Comments

Sort By

Login or Register to join the conversation

adeoweb 5 years ago edited

Hi. Just watched this tutorial and an idea popped into my head. What if we dispatched query message from controller through a transport (to handle it asynchronously), then executed some logic in controller and then wait for a message to be handled? That way we could run some code in parallel to query handling. For example:


$envelope = $queryBus->dispatch(new GetTotalImageCount());

// Insert some important logic here //

$handled = $envelope->last(HandledStamp::class);
while(!$handled instanceof HandledStamp::class) {
    sleep 1;
}
$imageCount = $handled->getResult();

Would this work?

|

weaverryan SFCASTS adeoweb 5 years ago edited

Hey Adeoweb!

Hmm, interesting. On a high level, I think it *would* work... but you'd have a few challenges and problems. The biggest one is if your workers are busy... like maybe it takes 30 seconds to find the time to handle your message. That's... not too much fun. Even a quick response could take 1/2 a second, which in "web request" time is really long. So... it's tricky to get this to happen in practice, in large part because the philosophy of works is that the work is done "as quickly as possible"... but some delays are no huge problem, since nobody is waiting for the info.

You would also need to implement some extra logic in Messenger to make it work, but due to the above problems, you won't see that functionality. I'm sure *someone* has done this *somewhere* and gotten decent results, I just don't know an example. Maybe a microservice architecture might be the best example. Imagine you dispatch a message *synchronously*, but the handler actually sends an API request to some other service which (again, synchronously) does some work and sense back the answer. Then, once all of that finishes, in your controller, you can read the result. The end result is actually quite close to what you're proposing. You send the message async, but doe to the "sleep", in reality, everything happens sync anyways.

Let me know if that made any sense ;)

Cheers!

|

adeoweb weaverryan 5 years ago

Well, my idea was running multiple tasks in parallel at the same time and then synchronizing the main thread with all those threads. For example in javascript you can create one (or more) promises so they all could be handled in the background at the same time, in parallel. Then, while all the promises are being handled, the main thread could do some other work (at the same time, in parallel to promises) and then you can wait for all the promises to finish. You can do similar things in C# using tasks - you can create multiple tasks, so they can run in parallel at the same time, and when you need to synchronize your main thread with these tasks, you can await them. So microservice approach is not really fitting here.

I've got your point in the first paragraph. To solve the problem, one could implement some extra logic that would spawn PHP message handler process for every message dispatched. That way we would have a true multithreading system in PHP just like in C#. Maybe I will test my idea when I will have more free time. I will post the results here in a reply.

Thank you!

|

weaverryan SFCASTS adeoweb 5 years ago edited

Hey Adeoweb!

Ah, I understand better now! There is a new feature (that I have not looked into yet) in PHP 8.1 called Fibers - https://betterprogramming.p... - that might (or might not) be somewhat related to what you're saying :).

Anyways, let me know if you do some experimenting!

Cheers!

|

Shiraats 6 years ago

HI.
Any reason why this video has not been released yet

|

MolloKhan SFCASTS Shiraats 6 years ago

Hey!

Good question. The thing here is that this is not the last video of the course. Ryan is preparing more content but at the same time we are actively releasing the "ApiPlatform Security" tutorial. We just need some more time :)

Cheers!

|

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