title: Azure Functions: Understanding Change Feed in the context of multiple apps
body: <p>According to the below diagram on <a href="https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-processor" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-processor</a>, at least 4 partition key ranges are distributed between two hosts. What I'm struggling to understand in this diagram is the distinction between a host and a consumer. In the context of <code>Azure Functions</code>, would it be true to say that a host is a <code>Function</code> app whereas a consumer is an active/warm instance?</p>
  <p><a href="https://i.stack.imgur.com/vDjpY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vDjpY.png" alt="enter image description here" /></a></p>
  <p>I'd like to create a setup with N many <code>Function</code> apps each with 0-200 active instances (depending on workload). At the same time, I'd like to read <code>Change Feed</code>. If I use a <code>CosmosDBTrigger</code> with the same connection string and lease container in each app, is this taken care of automatically or do I need a manual implementation?</p>