¡Messenger! Encola el trabajo para Despues

Hey skyCatalysm,

Thank you for your interest in this screencast, your vote is counted. We do plan to record it some day, but unfortunately, we don't have any estimations yet - too many good stuff we would like to work on before it.

Thank you for your patience!

Cheers!

Hey @Aries

Yes, all of the concepts are still relevant. Also, when there's a significant change we add notes about it

Cheers!

Thanks @MolloKhan

Hey Robert W.

You're totally right. The Doctrine version that Symfony 4.4 uses has a few structural changes and most importantly, they dropped their cache implementation (that's why you had to removed the cache bundle).

Thanks for sharing your solution with others. Cheers!

Hey Abdul,

You can take a look at these videos if you're interested in CORS: https://symfonycasts.com/se... - that's all we have so far.

I hope this helps!

Unfortunately, no standalone courses about it yet, but you can track status of this in our idea pool here:
- https://symfonycasts.uservo...
- https://symfonycasts.uservo...

Cheers!

Hey Kiuega,

Thank you for your interest in SymfonyCasts tutorials!

The only official way to know what's the next: https://symfonycasts.com/co... - there's the upcoming tutorials, and we do try to keep them in the order we will going to release them. Yes, we're working on EasyAdminBundle v3, but I don't think it will be next yet. For now we're actively releasing VueJS ep2 here: https://symfonycasts.com/sc...

Thank you for your patience and anderstadning!

Cheers!

Hello again erop :)

Form my point of view this breaks the main idea of queue. Looks like you want to do a Soviet queue where you can go and take anything from queue by some criteria, but not by order. In normal queue messages should be processed by handler one by one in some sort of order when they are ready to be processed, and not when you are ready to take it.

BTW I think you can use shared Redis connection with TTL on keys. It can totally fit your idea.

Hope, I haven't missed something and understand your idea correctly!

Cheers!

Hey, sadikoff !
Yeah, I knew the idea was a trash :) Frankly I just wanted "to cut the corner" as in Redis case I need to build a special Redis storage service. As I understood I can not use "native" Symfony namespaced cache pool based on cache.adapter.redis since CacheInterface is not enough for a given use case. Moreover I need to implement the same "namespacing" concept for this "special" Redis store. OK... As I said I just wanted "to hack the system" using stamp technique :) Thanks you, Vladimir!

erop Of course it depends on what you need, but building a special service can be an easiest thing you can do in that case :)

Cheers!

Hey erop

In theory you should run consuming command with separate debug configuration, and you should be able to connect it to phpstorm. Because it's cli process consuming this async messages.

Cheers!

You are my hero, sadikoff !

Hey William,

For solving this task you would need to use a different solution called CRON. With this tool, that you can easily use on Unix systems, you can set up any tasks to be executed by specific schedule, like every hour, day, month, etc. Please, read about it, there's plenty of information all over the internet. Messenger in turn just helps to solve the problem with queues.

I hope this helps!

Cheers!

Hi Sir thank very much for your reply. Please i have a question. I would like to do planification task, i would like to save some task in the database and then execute a schedule method dynamically depend on the entry in database. So i want to read planification entity and generate cron with some service.

Please how can i achieve this with symfony ?

Hey William,

I'm not sure I completely understand your task. But usually, CRON is something that you do not generate dynamically. You create a Symfony command, and then set up it to be executed on some schedule. It's more manual process to figure out how often this command should run. And inside the command, you need to have a logic that will check if any work should be done or not. If not, like for example, no entities in the DB that should be processed - then just return. If some work should be done - then process. Something like this.

I hope this helps!

Cheers!

Hey @ElGovanni!

I think, even if you don’t have any heavy work, Messenger enables this “command bus design pattern”. If you love that pattern, it’s awesome. If you don’t care so much, then yea, there’s much less use for it. So, it’s useful for any tasks that are heavy OR if you just want to leverage the command bus pattern.

Cheers!

it's useful for any tasks that are heavy

Like sending e-mail by symfony mailer?

Hey Stefan T.

Yes, that's a good use case. Writing a big file is another good example

Cheers!

Hey Skylar!

I don't think that specific topic will make it into this tutorial, so I'll give you some tips here :). The main reason is that (delightfully) there is nothing special about unit testing a handler. If you think about it, a handler is no different than any other service you might build in your app - it's a service, it uses dependency injection and it has a public method that "does" something. The only difference is that the method is called __invoke, which means that when you're calling it in your test, instead of $myService->myMethod('fooArg') it will be $myService('fooArg') (you execute the object like a function).

The one other interesting thing about a handler is that they (unless you're using messenger as a query bus... but, different topic) never return anything. That's not a strict requirement - messenger doesn't care if you do - but you typically don't, because Messenger doesn't care about your return value (and neither should you when you dispatch to Messenger). This means that your unit tests will typically be testing what a handler function does instead of what it returns - e.g. you might test that it calls flush() on the entity manager. If you find that there are some other things internally that you'd like to test but are having trouble (for example, you want to test that an entity was created and with the correct data... before being saved), it's probably a sign that you should refactor that small piece you want to test into its own service, test that, then autowire the new service into your handler.

Let me know if this helps! If i missed the heart of your question, definitely tell me ;).

Cheers!

I get what your saying and it makes sense. I was going to swallow the whole dragon and test from the message dispatch to the results of the handlers work in one test.

Thank again for your time. It's always appreciated.