How duikboot/flask-docker-celery-rabbitmq works
This is a small Flask/Celery demo for submitting asynchronous work, running single or grouped processing tasks, and querying task status. The main workflow is an HTTP request to the Flask API, Celery dispatch through RabbitMQ to workers, and a status request that reads the task result. The README also documents Flower monitoring and PostgreSQL, but says PostgreSQL is not used. Worker execution and monitoring relationships are based on README statements; deployment details beyond those statements are not mapped.
Main entry points: api/__init__.py API Routes · tasks/__init__.py Celery Tasks · app.py Flask Application · celery_worker.py Celery Worker
Components 11
Web API
- Flask Application
app.py - Environment Configuration
config/settings.py - API Routes
api/__init__.py - Task Status
api/__init__.py
Task Processing
- Celery Tasks
tasks/__init__.py - Bulk Task Group
tasks/__init__.py - Celery Worker
tasks/celery_worker.py
Queue and Monitoring
- RabbitMQ Broker
- RPC Result Backend
- Flower Monitor
Other components
- HTTP Client
Connections 13
- HTTP Client → Flask Application: sends HTTP
README.md - Flask Application → Environment Configuration: loads settings
app.py - Flask Application → API Routes: registers routes
app.py - HTTP Client → API Routes: submits work
README.md - API Routes → Celery Tasks: delays task
api/__init__.py - API Routes → Bulk Task Group: calls task
api/__init__.py - Bulk Task Group → Celery Tasks: groups tasks
tasks/__init__.py - Celery Tasks → RabbitMQ Broker: dispatches work
tasks/__init__.py - Celery Worker → Celery Tasks: runs tasks
README.md - Celery Worker → RabbitMQ Broker: consumes work
README.md - HTTP Client → Task Status: requests status
README.md - Task Status → RPC Result Backend: reads task result
api/__init__.py - Flower Monitor → Celery Worker: monitors distribution
README.md