PHPBenelux Conference 2015
23 - 24 Jan 2015 at Hotel Ter Elst

Good short talk on XHprof, XHgui and link0/profiler.

Great info in some of the basic approaches you can take to setup a microservice-driven (that's a word, I called it) project. Whether the approach is viable or not is aside this talk.

I liked that together with explaining the concept I was also given the tools and examples to do this. I had a few questions in my head during the talk but at the end of the talk all of them were answered.

Very inspiring and a nice way of executing experiments. I can't help but think that Mathias casually carries a stack of sticky notes everywhere he goes.

I feel like all I got from the talk were the benefits of migrating to DDD. I would've liked to see some more in-depth view into what happened.

Also it started off with the speaker talking to the ground instead of the audience, but that improved along the way.

BEST... SOCIAL... EVER!

The slides showed good insight of properly refactoring coupled code to event driven code. The question opportunities in between the sections were good (even though none were asked).

This talk is an introduction to harnessing the power of a mediator, and for that purpose it was great.

I loved the simulator, it was a great help in understanding the infrastructure of RabbitMQ.

Great talk to have people realise how easy it is to monitor performance and find your bottlenecks.

Inspiring, insightful and motivational.

Like said before, the incremental refactoring was really interesting and helpful.

The title really appealed to me as I'm as of late interested in events as used in event sourcing. This was not really in the scope of this talk, I realized, but maybe it's nice to incorporate some concepts of this in a 'further reading' section in the talk. So here I go :)

Maybe you could be more explicit in defining the difference between a command and an event. And explain how an event can trigger a whole chain of changes. Maybe even see the user as an event generator and the system as completely event driven. Although this might be too far fetched :)

And, if you could find time in the presentation, you could maybe gloss over a way of distributing events from one piece of software to another (from a PHP application which receives the initial command over to a NodeJS application which receives the events generated by that command, and then generates events locally in the JS application, for example), effectively crossing the application boundary. And beyond that maybe cross the machine boundary.
I think this would tie in nicely with micro-services and scaling applications.

Event sourcing and CQRS are out of the scope of this introduction to events, conceptual refactoring and loose coupling. But with these additions, I think it, should be a good primer for future talks.