Is active and passive consumers baked into the Azure EventHubs SDK? I'm looking implement one active consumer and one or more passive/fallback consumers if the active one were to go offline. Ideally it'd be an automated process where I can spin up multiple instances of the same application on multiple servers, then have the applications automatically resolve which instance should be processing messages. I've read through Azure's documentation, and it appears to be possible, though in-depth information is not provided. The documentation states how they recommend only having one active reader, but they don't mention how that is implemented. Does that mean only one instance of my consuming application can be up and running at any given time? Or is there a configuration which can control how many active consumers are allowed? For this project, we're using the EventHubConsumerClient class, not the EventProcessorClient.
EventHub structure: Partition 0: Consumer 0: Active, my application is up and running and is processing messages. Consumer 1: Active, my application is up and running but idle as Consumer 0 is active. Partition 1: Consumer 0: Active, my application is up and running and is processing messages. Consumer 1: Active, my application is up and running but idle as Consumer 0 is active.
