When do you choose prefork, gevent, or solo worker pools?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
prefork (default) uses processes and is the safe choice for CPU and for C extensions that are not greenlet-safe.
WHY — Celery instead of guessing?
Why interviewers care about Celery:
on Celery.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1prefork (default) uses processes
and is the safe choice for CPU and for C extensions that are not greenlet-safe.
- 2gevent/eventlet suit high-concurrency I/O
if every dependency is patched.
- 3solo is one process,
useful for debugging, not for production throughput.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
prefork (default) uses processes and is the safe choice for CPU and for C extensions that are not greenlet-safe. gevent/eventlet suit high-concurrency I/O if every dependency is patched.