title: Web architecture for "sharing" API calls between users
body: <p>I recently posted a question: <a href="https://stackoverflow.com/questions/67926686/how-to-dynamically-create-and-close-infinitely-running-celery-tasks-using-django">How to dynamically create and close infinitely running Celery tasks using Django Channels</a> . But Django channels seems to be a fairly niche area of development so I'd like to open up the question as a question about general architecture patterns.</p>
  <p>I would ultimately like users of my application to tap into the same data streams dynamically.
  I am creating a cryptocurrency application where users are accessing the same live price data.
  It seems ridiculous that every user should have to request an API for the same information.</p>
  <h4>Scenario:</h4>
  <p><code>Multiple users are receiving BTC/USD data by API request. How can I get this data and share it between users?</code></p>
  <p>This problem must have been solved countless times but I'm finding it very difficult to find the correct method for setting up a scalable solution.</p>