In common use cases for Event Hub, you need a producer and a consumer to fetch data and process it. Let's consider the following scenario:
In this scenario, we have two consumers:
- Consumer 1 for some generic processing
- Consumer 2 for archiving events
We also introduced storage for storing a log of events. As you can see, the downside of that solution is the fact that you need to maintain both consumers—two code bases and two instances. With Event Hub Capture, the scenario we are considering now will change a little bit:
Now we no longer require additional consumers as it will be Event Hub Capture's responsibility ...
