|  | @@ -22,15 +22,18 @@ more worker servers. Tasks can execute asynchronously (in the background) or syn
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  Celery is already used in production to process millions of tasks a day.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -Celery was originally created for use with Django, but this is no longer
 | 
	
		
			
				|  |  | -the case. If you want to use Celery in a Django project you need to use
 | 
	
		
			
				|  |  | -`django-celery`_. It can also `operate with other languages via webhooks`_.
 | 
	
		
			
				|  |  | +Celery is written in Python, but the protocol can be implemented in any
 | 
	
		
			
				|  |  | +language. It can also `operate with other languages using webhooks`_.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  The recommended message broker is `RabbitMQ`_, but support for Redis and
 | 
	
		
			
				|  |  | -databases is also available.
 | 
	
		
			
				|  |  | +databases (`SQLAlchemy`_) is also available.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | +You may also be pleased to know that full Django integration exists
 | 
	
		
			
				|  |  | +via the `django-celery`_ package.
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +.. _`SQLAlchemy`: http://www.sqlalchemy.org/
 | 
	
		
			
				|  |  |  .. _`django-celery`: http://pypi.python.org/pypi/django-celery
 | 
	
		
			
				|  |  | -.. _`operate with other languages via webhooks`:
 | 
	
		
			
				|  |  | +.. _`operate with other languages using webhooks`:
 | 
	
		
			
				|  |  |      http://ask.github.com/celery/userguide/remote-tasks.html
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  Overview
 |