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

Best practice on using grocer for large scale push notifications #114

Closed
ebalassanian opened this issue Jun 23, 2016 · 2 comments
Closed

Comments

@ebalassanian
Copy link

I need to send notifications to a large number of devices (> 100K scaling to 1M). These notifications are triggered from client interaction with server side objects. Obviously I can't send these out inline so I'm looking at solutions to send the notifications asynchronously (e.g. sidekiq or delayed job). Are there existing best practices for achieving this with Grocer?

@stevenharman
Copy link
Member

Hello @ebalassanian,

That is basically the same use case we had when we originally built Grocer. We had a large number of iOS clients and a Rails app. The Rails app would send notifications via Grocer, in a Resque job. Grocer has no dependencies on Rails nor any specific background job library. It's just Ruby and so can be integrated with any of those libraries.

@stevenharman
Copy link
Member

I'm closing this for now. Please re-open if you have specific questions.

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