It depends on what do you use Celery for.<p>For launching a bunch of IO-bound &quot;tasks&quot;, for example calling external services from Django views, I&#x27;d consider using Twisted (or Tornado, or asyncio). Your tasks would need to be either written in async style, or you&#x27;d need to spawn new processes from within Twisted (but built-in functionality makes this rather easy). Still, Twisted is <i>rock-solid</i>, doesn&#x27;t leak and is capable of handling <i>a lot</i> of (IO-bound) tasks concurrently.<p>If your tasks are CPU bound you pretty much have no choice other than something based on multiprocessing. You can still use Twisted, but only in the second way. If the code of your tasks doesn&#x27;t use C extensions you could use Jython with threads. This way you&#x27;d get parallelism without having to rewrite much code.<p>If you need your tasks parallelized and you want to run a lot of them concurrently then I&#x27;m afraid you&#x27;re out of options in Pythonland. Personally I&#x27;d go for Erlang with ErlPort, but I know Erlang rather well.<p>On the other hand, Celery is a nice piece of code. I think in most cases you don&#x27;t need anything else, or at least nothing drastically different, like the options above. Perhaps rq would be a good idea. I also encountered an interesting project called Pulsar (<a href="http:&#x2F;&#x2F;pythonhosted.org&#x2F;pulsar&#x2F;overview.html" rel="nofollow">http:&#x2F;&#x2F;pythonhosted.org&#x2F;pulsar&#x2F;overview.html</a>), but it seems to be usable only on 3.3 and above.