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

Investigate MicahParks/websocket-pubsub #5

Open
thisisaaronland opened this issue Nov 18, 2021 · 1 comment
Open

Investigate MicahParks/websocket-pubsub #5

thisisaaronland opened this issue Nov 18, 2021 · 1 comment

Comments

@thisisaaronland
Copy link
Member

https://github.com/MicahParks/websocket-pubsub

Are there approaches and improvements that can be integrated here?

@MicahParks
Copy link

I'd love for that project to be used in open source! It's served me well in a handful of closed source projects.

If you need more examples or additional documentation, please feel free to reach out.

Be sure to consider it's scaling design decision before incorporating it into a project:

All assets for this project are stored in memory. This means the pubsub server scales vertically with its sole host's processing power, memory, and network.

The primary use case for this pubsub server is smaller projects where it makes sense to separate publisher and subscriber logic into different programs or hosts/containers.

This pubsub server is not recommended for larger projects that need to scale a pubsub server past the resources available on a single host.

I do have future plans to implement MicahParks/websocket-pubsub#2. This could help reduce load on the central pubsub server by allowing users to connect their own server as a proxy. Reducing the active connections on the primary server.

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

2 participants