A while ago I wrote about using exec and shell commands to manage multiple PHP processes. One of the questions that came up was; “how does this differ from what’s out there?”
The post is going to be a bit of a mixed bag. I’ve been working on a parallel-execution library, and I want to look at how it can be used with an event loop. Before that though, I want to look at a few parallel-execution libraries intended to be used…
Let’s talk about asynchronous PHP code. There are more ways to make PHP code execute asynchronously and in parallel than there are reasons you can think of for wanting to do it in the first place.
Given the case for asynchronous PHP, you may be keen to try it but unsure where to start. Perhaps you’ve been working on an API, and you want to add socket support. Let me show you how!
You can find the code on Github. You can find the discussion on Reddit. You should…
Last week I got the opportunity to share recent work with my colleagues, at SilverStripe. I was going to present Async PHP today, but since I covered ReactPHP last week; I decided to talk…
A few days ago, our lovely Development Manager asked me to share at Show and Tell. It’s a Friday-event where a couple of people, here at SilverStripe, talk a bit about some of the recent work they’ve done.
Creating reactive applications is hard. As a community, we PHP developers have been writing blocking code behind web servers like Apache and Nginx, for ages. We’re just not used to using the event-loop and reducing/removing blocking IO.
As PHP developers, we’ve been conditioned to fear sockets. “PHP scripts should die quickly”; some say. Still others; “Why don’t you use Node for that?”.
The problem is that these arguments shut down any attempts to evolve core PHP, and the surrounding ecosystem.
