Asynchronous event processing

Jan Gregor Triebel , Dennis Oehme (24.Mar.2016 at 19:30, 45 min)
Talk at PHPUGFFM II/2016 (English - US)

Rating: 4 of 5

Asynchronous event processing

Who are you?

Claim talk

Talk claims have been moved to the new site.

Please login to the new site to claim your talk

Comments closed.


Rating: 5 of 5

24.Mar.2016 at 20:55 by Sascha Schuh (31 comments) via iPhone app

I saw this talk on symfony ug, too. It was again very interesting!

Rating: 4 of 5

24.Mar.2016 at 20:59 by Marco Pivetta (117 comments) via Web2 LIVE

Plus: very valid and useful points, and actually had a chance to learn a few practical things from folks that use queues with high load environments.
Minus: not really about events, but just about async job handling

Rating: 4 of 5

25.Mar.2016 at 09:33 by Marat (12 comments) via Web2 LIVE

+ It was very interesting, experience-based presentation.
- Code demonstration was with very small font size.

Rating: 4 of 5

28.Mar.2016 at 10:28 by Stephan Hochdörfer (206 comments)

Pretty good overview on how to offload tasks from your main web server. To improve the talk I would rather focus on one specific technology and deeply cover the problems you guys ran into (I guess a lot given my experience *g*) or find a better way to compare the different technologies you tested (e.g. when to use which technology). Other than that very well presented, would love to see more presentations from you guys.

Rating: 4 of 5

29.Mar.2016 at 15:56 by David Manners (40 comments) via Web2 LIVE

Nice talk to get you thinking about asynchronous event processing. I really enjoyed the fact that the presenters showed you how they messed up during the learning process. Could do with making the code easier to read in future but overall a very solid talk.

Rating: 4 of 5

29.Mar.2016 at 18:10 by Claudio (38 comments) via Web2 LIVE

Actually, It's not suitable for me to rate this talk, because I missed the first few slides, so I don't write about if something came short.

The most interesting part for me was the communication with the queue and the re-queue, because of the experiences they made, their answers to performance and error handling.

© 2019