<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 00:30:22 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Scalability and Responsiveness with Zend Platform's Job Queue]]></title>
      <guid>http://www.phpdeveloper.org/news/8097</guid>
      <link>http://www.phpdeveloper.org/news/8097</link>
      <description><![CDATA[<p>
On the Zend Developer Zone today, there's <a href="http://devzone.zend.com/article/2207-Scalability-and-Responsiveness-with-Zend-Platforms-Job-Queue">a new article</a> by <i>Dotan Perry</i> and <i>Shie Erlich</i> talking about what kind of scalability and responsiveness that the Zend Platform's Job Queue functionality has to offer.
</p>
<blockquote>
The <a href="http://www.zend.com/products/zend_platform">Zend Platform</a> 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.
</blockquote>
<p>
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:
</p>
<ul>
<li>Step 1: Off Load to a Dedicated Server
<li>Step 2: Scheduling to low-traffic hours
<li>Step 3: Breaking down tasks using dependencies
<li>Step 4: A recurring cleanup job
</ul>
<p>
They also include an explanation as to why this method is preferable over just using croned scripts for the same purpose.
</p>]]></description>
      <pubDate>Thu, 21 Jun 2007 11:24:00 -0500</pubDate>
    </item>
  </channel>
</rss>
