Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a system wide subscription system that allows more efficient subscribing of streams to avoid duplicate traffic in most cases #36

Open
daviddawson opened this issue May 26, 2017 · 0 comments

Comments

@daviddawson
Copy link
Member

Currently every subscription is independent.

If 10 services are subscribed to the same stream, they will all be sent the data, leading to 10 times as much traffic.

Since most of them will remain in lockstep most of the time, a single subscription could be used, most of the time, distributing the events out as they are received.

The only time this will not be the case is when a service needs to perform a full or partial replay of a stream. Eg, If a recovery is required or a view is being upgraded.

In this case, a separate subscription should be created, then when the subscription approaches the current main subcription, it should be shut down and the service then start taking events from the main subscription.

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

No branches or pull requests

1 participant