Databases
StackOverflow2013
Postsdbo
POIs Celery appropriate for use with many small, distributed systems?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs Celery appropriate for use with many small, distributed systems?
    primarykey
    data
    text
    <p>I'm writing some software which will manage a few hundred <a href="http://beagleboard.org/" rel="noreferrer">small systems</a> in “the field” over an intermittent <a href="http://en.wikipedia.org/wiki/3G" rel="noreferrer">3G</a> (or similar) connection.</p> <p>Home base will need to send jobs to the systems in the field (eg, “report on your status”, “update your software”, etc), and the systems in the field will need to send jobs back to the server (eg, “a failure has been detected”, “here is some data”, etc).</p> <p>I've spent some time looking at <a href="http://celeryproject.org/" rel="noreferrer">Celery</a> and it <em>seems</em> to be a perfect fit: <code>celeryd</code> running at home base could collect jobs for the systems in the field, a <code>celeryd</code> running on the field systems could collect jobs for the server, and these jobs could be exchanged as clients become available.</p> <p>So, is Celery a good fit for this problem? Specifically:</p> <ul> <li>The majority of tasks will be directed to an individual worker (eg, “send the ‘get_status’ job to ‘system51’”) — will this be a problem?</li> <li>Does it gracefully handle adverse network conditions (like, eg, connections dying)?</li> <li>What functionality is only available if RabbitMQ is being used as a backend? (I'd rather not run RabbitMQ on the field systems)</li> <li>Is there any other reason Celery could make my life difficult if I use it like I've described?</li> </ul> <p>Thanks!</p> <p>(it would be valid to suggest that Celery is overkill, but there are other reasons that it would make my life easier, so I would like to consider it)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDavid Wolever
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs Celery appropriate for use with many small, distributed systems?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs Celery appropriate for use with many small, distributed systems?
      1. USasksol
      1. VTFavorite
    3. VO
      singulars
      1. POIs Celery appropriate for use with many small, distributed systems?
      1. USDominique Guardiola
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload