[url]http://celeryq.org/[/url]
[b]Overview[/b]
This is a high level overview of the architecture.
[img]http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg[/img]
he broker delivers tasks to the worker servers. A worker server is a networked machine running celeryd. This can be one or more machines depending on the workload.
The result of the task can be stored for later retrieval (called its “tombstone”).
[b]Task Queue by HTTP call Work flow[/b]
[img]http://dl.iteye.com/upload/attachment/317689/b3db18c6-0da0-3ae3-879d-467d5ef7ab40.jpg[/img]
[b]Overview[/b]
This is a high level overview of the architecture.
[img]http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg[/img]
he broker delivers tasks to the worker servers. A worker server is a networked machine running celeryd. This can be one or more machines depending on the workload.
The result of the task can be stored for later retrieval (called its “tombstone”).
[b]Task Queue by HTTP call Work flow[/b]
[img]http://dl.iteye.com/upload/attachment/317689/b3db18c6-0da0-3ae3-879d-467d5ef7ab40.jpg[/img]