In his newly updated blog today (changed to WordPress) Kevin Schroeder has a new post looking at a new queuing library available for Zend Server's Job Queue including an example of its use.

This will probably be one of the last posts I do on the Zend Server Job Queue functionality. From this point on they will probably be less frequent, though I'm sure several posts will allude to it. The reason I'm going to put it on the back burner is because I have written a library which is now available on GitHub. What it does is encapsulate all of the functionality that I think needs to be there to be able to implement asynchronous functionality.

In his example code, he shows how to use the library to create a job class that sends a basic email to a defined address and how to set it up with the Manager. Then the action can be called from a script getting the remote job and checking to see when the job has finished.

On the Zend Developer Zone today there's a new post (technically a repost) of an article from Kevin Schroeder about using the job queue in the Zend Server software to enhance the functionality of your application.

When talking about building a scalable application there is a big concept out there that many PHP developers are not overly familiar with. That concept is queuing. It is becoming much more prevalent in PHP-land but the concept of a queue is still relatively unused among PHP developers. [...] Queuing a job is actually very easy to do. A job is run by calling a URL where that job resides. The Job Queue daemon will receive the request from your application and will then call the URL that you specified in the API call. Once you call that URL your application can continue going on its merry way to finish serving up the request.

He includes some code snippets showing how to create the request - in this case a simple call that will just email when the job is preformed. There's more than one way to do it and he includes a more well structured/less scripty way to do things in an abstract class.

On the Zend Developer Zone today, there's a new article by Dotan Perry and Shie Erlich talking about what kind of scalability and responsiveness that the Zend Platform's Job Queue functionality has to offer.

The Zend Platform Job Queue is used to make applications more responsive by allowing tasks to be performed on other machines (e.g.: dedicated machine), and scheduling tasks to a future time (usually to low-traffic hours). [...] Job Queue offers both a web-based management UI, and a programmer-oriented rich API, which allows embedding sophisticated logic into applications. This article will demonstrate basic usage of Job Queue, through an imaginary company wesellalot.com.

They start by presenting a scenario where a simple cluster of machines behind a load balancer all work with the same database. Because of some of the tasks they want to perform, things could get overloaded very easily under a high load. Enter the Job Queue and their four step process to integrate it into this setup:

• Step 1: Off Load to a Dedicated Server
• Step 2: Scheduling to low-traffic hours
• Step 3: Breaking down tasks using dependencies
• Step 4: A recurring cleanup job

They also include an explanation as to why this method is preferable over just using croned scripts for the same purpose.

On the Zend Developer Zone today, there's a new article by Dotan Perry and Shie Erlich talking about what kind of scalability and responsiveness that the Zend Platform's Job Queue functionality has to offer.

The Zend Platform Job Queue is used to make applications more responsive by allowing tasks to be performed on other machines (e.g.: dedicated machine), and scheduling tasks to a future time (usually to low-traffic hours). [...] Job Queue offers both a web-based management UI, and a programmer-oriented rich API, which allows embedding sophisticated logic into applications. This article will demonstrate basic usage of Job Queue, through an imaginary company wesellalot.com.

They start by presenting a scenario where a simple cluster of machines behind a load balancer all work with the same database. Because of some of the tasks they want to perform, things could get overloaded very easily under a high load. Enter the Job Queue and their four step process to integrate it into this setup:

• Step 1: Off Load to a Dedicated Server
• Step 2: Scheduling to low-traffic hours
• Step 3: Breaking down tasks using dependencies
• Step 4: A recurring cleanup job

They also include an explanation as to why this method is preferable over just using croned scripts for the same purpose.