How mher/node-celery works
Main Components
a. Client Application Layer:
• Node.js application using the node-celery client
• Main client interface (celery.createClient())
• Event handling system (error, connect events)
b. Message Broker Layer:
• Both supported message brokers:
• RabbitMQ (AMQP)
• Redis
• Broker configuration options
• SSL/Security configurations for RabbitMQ
c. Result Backend Layer:
• Both supported backends:
• AMQP (RabbitMQ)
• Redis
• Different result handling mechanisms:
• Polling (Redis)
• Event-based (AMQP)
d. Celery Worker Layer:
• Connection to actual Celery workers
• Task routing capabilities
• Queue management
Connection Flows
• Task Publication Flow:
• Client → Message Broker → Celery Workers
• Result Retrieval Flow:
• Celery Workers → Result Backend → Client
• Event Handling Flow:
• System Events (connect, error)
• Task Events (ready, result)
Special features
• Task Management:
• ETA scheduling
• Expiration handling
• Task routing
• Queue configuration
• Result Handling:
• Polling mechanism (Redis)
• Event-based results (AMQP)
• Task status tracking