Note: I'm migrating from gonzalo123.com to here. When I finish I'll swap the DNS to here. The "official" blog will be always gonzalo123.com

      Enqueue Symfony's process components with PHP and ZeroMQ

      Today I’d like to play with ZeroMQ. ZeroMQ is a great tool to work with sockets. I will show you the problem that I want to solve: One web application needs to execute background processes but I need to execute those processes in order. Two users cannot execute one process at the same time. OK, if we face to this problem we can use Gearman. I’ve written various posts about Gearman (here and here for example). But today I want to play with ZeroMQ.

      I’m going to use one great library called React. With react (reactor pattern implementation in PHP) we can do various thing. One of them are ZeroMQ bindings.

      In this simple example we are going to build a simple server and client. The client will send to the server one string that the server will enqueue and executes using the Symfony’s Process component.

      Here is the client:

      <?php
      include __DIR__ . '/../vendor/autoload.php';
       
      use Zmqlifo\Client;
       
      $queue = Client::factory('tcp://127.0.0.1:4444');
      echo $queue->run("ls -latr")->getOutput();
      echo $queue->run("pwd")->getOutput();
      

      And finally the server:

      <?php
      include __DIR__ . '/../vendor/autoload.php';
       
      use Symfony\Component\Process\Process;
      use Zmqlifo\Server;
       
      $server = Server::factory('tcp://127.0.0.1:4444');
      $server->registerOnMessageCallback(function ($msg) {
          $process = new Process($msg);
          $process->setTimeout(3600);
          $process->run();
          return $process->getOutput();
      });
       
      $server->run();
      

      You can see the working example here:

      youtube

      you can check the full code of the library in github and Packagist.

      UPDATE As Igor Wiedler said React is not necessary here.

      ZMQ is used for blocking sends and blocking tasks, having an event loop does not really make much sense.

      github repository updated (thanks!).

      comments powered by Disqus