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

Implementing 'push_notifications_only' config :: Aws Only for now #136

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

2Taps
Copy link

@2Taps 2Taps commented Oct 30, 2017

Hey guys,

With this i have tried to implement a configuration parameter that allow me to use the bundle and aws provider only with the SNS to push messages to my backend, without SQS.

I know that SNS have the maximum retention time of 1 hour for messages but this is ok for my use case.

I also want to make the bundle able to configure/atach a delivery policy to be able to configure 'notification_retries' and 'retry_timeout' but until now i do not know how to do it.

If someone can help would be nice. Until i am able to do this, ill manually configure the delivery policy in SNS dashboard.

Please let me now if you find some problem with my changes.

Thank you!

@scrutinizer-notifier
Copy link

The inspection completed: 1 new issues

@2Taps
Copy link
Author

2Taps commented Oct 31, 2017

Maybe a better name for the option would be push_notifications_no_poll

@k-k
Copy link
Contributor

k-k commented Mar 28, 2018

@GuilhermeMoura1 I'm not sure if this would be a great idea, the point of the SQS queue was for the visibility timeout - since all subscribers are notified of the SNS message, it was a way to avoid having service workers from processing the same message concurrently.

If you remove SQS, you'd need to handle that situation yourself. Is that intended?

@2Taps
Copy link
Author

2Taps commented May 28, 2018

Hey Guys,

We subscribe one endpoint of our backend to SNS.
So SNS notify that endpoint and we have a load balancer in front that to direct the message to one of our webserver machines.

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

Successfully merging this pull request may close these issues.

3 participants