title: Single Redis Instance with multiple simultaneous uses
body: <p>So I know that redis is an in-memory data store, but I don't really understand that much about under the hood.</p>
  
  <p>My question is, if I have three separate uses for it, such as <a href="https://github.com/miguelgrinberg/python-socketio" rel="nofollow noreferrer">python-socketio</a> to enable multiple instances of the socket server, <a href="https://docs.celeryproject.org/en/latest/userguide/calling.html" rel="nofollow noreferrer">Celery</a> to send tasks to another microservice (which would also use the same redis instance), and just a standard <a href="https://stackoverflow.com/questions/52596096/flask-socketio-redis-subscribe">subscriber</a> to listen for notifications to emit, can I use the same redis instance for all three tasks, or will I run into collisions between the different data (i.e celery misinterpreting a call to python-socketio as a task)?</p>