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.

Sign up for GitHub

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

Jump to bottom

How do I scale this? #231

Closed
thelinuxlich opened this issue Jun 6, 2016 · 2 comments
Closed

How do I scale this? #231

thelinuxlich opened this issue Jun 6, 2016 · 2 comments
Labels
question M-T: User needs support to use the project

Comments

@thelinuxlich
Copy link

It's just spawning processes whenever bottleneck happens and be happy?
@DEGoodmanWilson
Copy link

Howdy! Could you be more specific about what you are seeing, and what you were expecting to see? Along with steps to reproduce?

@DEGoodmanWilson DEGoodmanWilson added question M-T: User needs support to use the project Priority—Low labels Jun 24, 2016
@aoberoi
Copy link
Contributor

aoberoi commented Oct 3, 2017

i have a few comments about scalability, specifically horizontal scalability.

  1. using the new Events API for processing events rather than RTM gives you the ability to use traditional HTTP load balancers to scale. we released a dedicated node module for using it: @slack/events-api.

  2. the biggest challenge for scaling the RTM client would be the datastore API, since getting state out of the process is necessary for the approach you mentioned (spawning new processes). if you have any thoughts or input about this problem, join the discussion in Future of the DataStore API #330.

@aoberoi aoberoi closed this as completed Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question M-T: User needs support to use the project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thelinuxlich @aoberoi @DEGoodmanWilson