Celery-Redis Queue Setup & Audit

I have a FastAPI application that currently off-loads work to a simple background function, forcing every job to run one after another. The next milestone is to introduce a genuine queuing layer powered by Celery and Redis so tasks can be processed in parallel while still respecting priority levels (High, Medium, Low).

Your main mission is to wire this queue into the existing code-base, prove that the three priority bands are honoured, and make sure the solution remains maintainable as the workload grows. While that is the focus, I would also like a fresh set of eyes on the overall architecture and guidance on any quick wins we may have missed.

Once the code is solid, help me choose the right Azure services—Azure Cache for Redis, Container Apps, Kubernetes or another fit—and walk me through deploying the broker, workers and monitoring stack so everything runs smoothly in production.

Deliverables
• Celery + Redis integration with FastAPI, supporting High/Medium/Low priorities
• Written recommendations on code structure, scaling strategy and best practices
• Azure deployment plan and working deployment (scripts, YAML or Terraform acceptable)
• Short hand-over session or documentation so my team can operate the new stack confidently

If you have proven experience tuning Celery, dealing with task prioritisation and rolling it all out on Azure, I’d love to work with you.