Celery integration overview in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Celery in the context of Flask applications?

Celery is a tool that helps Flask apps run tasks in the background, so the app stays fast and responsive while doing heavy work separately.

intermediate

How does Celery communicate with Flask to run tasks asynchronously?

Celery uses a message broker like Redis or RabbitMQ to send and receive task messages between Flask and worker processes that run tasks in the background.

beginner

What is a 'worker' in Celery?

A worker is a separate process that listens for tasks from the message broker and runs them independently from the Flask app.

beginner

Why should you not run long tasks directly in Flask routes?

Running long tasks in Flask routes blocks the app, making users wait and slowing down responses. Celery moves these tasks to the background to keep the app fast.

intermediate

What are the main components needed to integrate Celery with Flask?

You need the Flask app, a Celery instance configured with the Flask app context, a message broker (like Redis), and worker processes to run tasks.

What role does Redis play in Celery integration with Flask?

A It acts as a message broker to queue tasks

B It stores the Flask app code

C It runs the Flask server

D It compiles Python code

Redis is commonly used as a message broker to queue tasks that Celery workers pick up and execute.

Which component runs the background tasks in Celery?

A Flask app

B Message broker

C Worker process

D Database

Worker processes listen to the message broker and execute the background tasks.

Why use Celery with Flask for long-running tasks?

A To make the app slower

B To avoid using a database

C To block user requests

D To run tasks asynchronously without blocking

Celery allows tasks to run asynchronously so the Flask app can respond quickly without waiting.

What must you configure to connect Celery with Flask?

A Database schema

B Celery instance with Flask app context

C Flask routes only

D HTML templates

Celery needs to be configured with the Flask app context to access app settings and resources.

Which of these is NOT a Celery component?

A Router

B Worker

C Scheduler

D Broker

Celery does not have a 'Router' component; it uses brokers, workers, and optionally schedulers.

Explain how Celery helps improve Flask app performance.

Think about what happens when a task takes a long time and how Celery handles it.

Describe the main steps to integrate Celery with a Flask application.

Consider what you need to connect and run for background tasks.

Practice

1. What is the main purpose of integrating Celery with a Flask application?

easy

A. To run tasks in the background without blocking the main app

B. To create HTML templates for the Flask app

C. To handle user authentication and sessions

D. To serve static files like images and CSS

Solution

1. Step 1: Understand Celery's role

   Celery is designed to run tasks asynchronously, meaning it handles work in the background.

2. Step 2: Connect to Flask app purpose

   Flask apps use Celery to keep the app responsive by offloading long tasks.

3. Final Answer:

   To run tasks in the background without blocking the main app -> Option A

4. Quick Check:

   Celery = background tasks [OK]

Hint: Celery = background task runner in Flask apps [OK]

Common Mistakes:

• Thinking Celery manages templates
• Confusing Celery with user login features
• Assuming Celery serves static files

2. Which of the following is the correct way to define a Celery task in a Flask app?

easy

A. @celery_app.task\ndef add(x, y): return x + y

B. celery_app.run_task(add)

C. @app.route('/task')\ndef task(): pass

D. def task(): pass

Solution

1. Step 1: Identify Celery task decorator

   Celery tasks are defined using the @celery_app.task decorator.

2. Step 2: Check syntax correctness

   @celery_app.task\ndef add(x, y): return x + y correctly decorates a function to become a Celery task.

3. Final Answer:

   @celery_app.task\ndef add(x, y): return x + y -> Option A

4. Quick Check:

   Celery task = @celery_app.task decorator [OK]

Hint: Use @celery_app.task to define tasks [OK]

Common Mistakes:

• Forgetting the @celery_app.task decorator
• Using Flask route decorators for tasks
• Calling celery_app.run_task which is invalid

3. Given this code snippet in a Flask app with Celery:

@celery_app.task
def multiply(x, y):
    return x * y

result = multiply.delay(3, 4)
print(result.get())

What will be printed?

medium

A. A task object reference

B. null

C. 12

D. An error because delay() is not valid

Solution

1. Step 1: Understand delay() usage

   Calling multiply.delay(3, 4) sends the task to Celery to run asynchronously.

2. Step 2: Using get() to wait for result

   result.get() waits for the task to finish and returns the output, which is 3 * 4 = 12.

3. Final Answer:

   12 -> Option C

4. Quick Check:

   delay() runs task, get() returns result [OK]

Hint: delay() runs task, get() fetches result [OK]

Common Mistakes:

• Thinking delay() returns the result immediately
• Confusing task object with result value
• Assuming delay() is invalid in Celery

4. You wrote this Celery task in your Flask app:

@celery_app.task
def add(x, y):
return x + y

But when you call add.delay(2, 3), it raises an IndentationError. What is the problem?

medium

A. delay() cannot be called on tasks

B. The function body is not indented properly

C. You forgot to import Celery

D. The decorator syntax is incorrect

Solution

1. Step 1: Check function indentation

   Python requires the function body to be indented under the def line.

2. Step 2: Identify error cause

   Here, return x + y is not indented, causing IndentationError.

3. Final Answer:

   The function body is not indented properly -> Option B

4. Quick Check:

   Python needs indented function bodies [OK]

Hint: Indent function body under def line [OK]

Common Mistakes:

• Ignoring Python indentation rules
• Assuming delay() is invalid
• Thinking decorator syntax is wrong

5. You want to integrate Celery with Flask using Redis as the broker. Which steps correctly describe the setup process?

hard

A. Install Celery only, define tasks without decorator, call tasks directly, no broker needed

B. Install Flask-Login, configure Celery with SQLite, define tasks with @app.route, call tasks with run()

C. Install Redis, configure Flask routes for tasks, use delay() without decorator, run Redis server

D. Install Redis, configure Celery with Redis URL, define tasks with @celery_app.task, call tasks with delay()

Solution

1. Step 1: Setup Redis broker

   Redis must be installed and running as the message broker for Celery.

2. Step 2: Configure Celery and define tasks

   Celery is configured with Redis URL, tasks use @celery_app.task, and are called with delay().

3. Final Answer:

   Install Redis, configure Celery with Redis URL, define tasks with @celery_app.task, call tasks with delay() -> Option D

4. Quick Check:

   Redis + @celery_app.task + delay() = correct setup [OK]

Hint: Use Redis broker, @celery_app.task, and delay() calls [OK]

Common Mistakes:

• Using wrong broker like SQLite
• Defining tasks without decorator
• Calling tasks with run() or no broker