Scaling the event stream subscription

Hey everyone,

I was wondering if there are any strategies or practices people have for scaling the event subscriptions. For horizontally scaling, how would you go about having multiple machines subscribing to the event stream, processing each event once and only once? For vertically scaling, are there any benchmarks out there? Has anyone tested how many events/sec a generic VPS can subscribe to before maxing out? Just doing something simple with each one like logging it to the console.


You could deploy a Node.js application that just subscribes to the event stream and creates a job in a remote queue like this one for each event. Then your multiple machines pull jobs from the queue and take however long to process them.

If you’re concerned with scaling, take a look at Azure EventHub. It can handle ingesting streams of up to 1 Gb/s!

1 Like