Skip to content
This repository has been archived by the owner on Dec 10, 2018. It is now read-only.

Deal / Document with Event Hubs limits #28

Open
clehene opened this issue May 16, 2017 · 3 comments
Open

Deal / Document with Event Hubs limits #28

clehene opened this issue May 16, 2017 · 3 comments
Assignees
Labels

Comments

@clehene
Copy link

clehene commented May 16, 2017

There's a hard limit of 20K messages per namespace. This may limit a users ability to use this with larger infrastructure.

Here are some details about quotas / limits
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-what-is-event-hubs

@aliostad
Copy link
Collaborator

Some discussions in issue #30 related to this.

In short:
If needs be, dedicated EventHub available that can do up to 2M event/second.
Also DocumentDB is not really a replacement, for cheaper option one could go for Kafka as IaaS on Azure.

@aliostad aliostad self-assigned this Jun 21, 2017
@aliostad
Copy link
Collaborator

@clehene are you happy with the explanation?

@gambrose
Copy link

@clehene can you elaborate where you get the 20K limit from?

I have quite recently started using event hubs. I needed to push a lot of small events and as there is a cost per event the costs would have been large. So I just batched my application events inside an event hub event. I also compressed the event payloads.

I don't know the size of the messages you are pushing but batching was at least an order magnitude cheaper for us.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants