The second day was a pretty funny for me. This one started when I left my friends and had gone to listen to presentations and they chose to eat breakfast instead. I think this happened just because of hunger – I decided to write to Anne Sophie and make a presentation during lighting talks. Crazy, huh? But, I’ll talk about this later, because a lot happened meanwhile.
Yesterday, me and my fellows from @XSolve arrived to Madrid at SymfonyCon Madrid 2014 conference. It’s the greatest and finest Symfony’s event in the year. A lot attendees came to listen about Symfony as a framework and as a success story.
Queuing in the background – getting started with RabbitMQ message broker
In PHP business logic is usually put right in action’s method or just behind it. Hence, every little piece of delaying and long-running code will be processed with a request. The problem is almost undetectable if a user sends an e-mail but with more complex actions it may take a little bit longer than preferred.
A couple of months ago I have started my adventure with CakePhp and as every Symfony’s developer I thought that any other framework except Symfony is a piece of crap. Day by day and step by step I began to realize that’s not so bad as it seemed to be in the beginning. Well, the second version of CakePhp still has a lot old-fashioned patterns, singletons or lack of tests, but I can live with that. I saw a lot of better or worse frameworks in my life. However, one module remains a bitter aftertaste – the router.
Event Driven Design is really popular topic for about two years and I don’t suprised this trend. You can really fast decouple parts of code without any influence on any other – you can send emails, saving logs or data to database without additional mess in your core class. Continue reading