The only bit I can contribute is making it message driven vs request driven. Push instead of poll. Poll systems have the added overheard of the balance between lag between requests and requesting too much.

In a very controlled, well administered messaging system, where jobs are "sent" out to others, you'll get uncanny, natural scaling vs a pull system where you're always tuning the pulling.

Polling is great for detecting when things happen with no sense of predictability, such as figuring out if a system was completely unplugged.

Consider that if you wish to create queue systems by hand.

- segue here -

Try putting permutations of those terms into google. You may find other systems as well. Tibco is supposed to be super awesome, but.. pricey.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.