I know POE much better than I know Gearman::Server, so I'm looking at Gearman::Server's documentation to answer this question.

Gearman::Server describes itself as an RPC dispatcher. Workers connect to it and register the jobs they can do. Clients connect to it and request work to be done. The Server routes work requests to the services that can handle them, and sends responses back. Unless I'm wrong, it's a basic message queue server.

POE is a general library for writing client/server programs, among other things. It's been used to write message queues, like POE-Component-MessageQueue. You could create something closer to Gearman::Server with it, maybe using something like POE-Component-IKC to handle service registration and request routing. But POE isn't a solution to that singular problem, like Gearman::Server is.

If all you need is Gearman, then it makes a lot of sense to go with that.

But if your requirements vary from Gearman, or you expect them to in the near future, then your time might be better spent by looking for a more suitable alternative. Message queuing, RPC dispatching, and load balancing are problems with a lot of existing solutions. Writing your own should be a last resort, but POE can help if you need to.


In reply to Re: Gearman::Server vs POE by rcaputo
in thread Gearman::Server vs POE by kulls

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.