Reputation: 3410
Scope:
I have an app that i am starting to build that has the "subscriber/publisher" situation on it's core.
For those who don't know, the idea behind this schema is that:
1) Someone creates a "Topic"
2) Endpoints subscribe to a "Topic"
3) Any message published to a certain "Topic" is pushed to the subscribers of said "Topic"
Considerations:
I am going to use Xamarin.IOS and Xamarin.Android as the framework to build this mobile app (so that it can be crossplatform from the begining).
RabbitMQ:
The RabbitMQ service is built on top of the AMQP pattern which solves my entire problem of modeling the "Topic/Subscriber/Publisher" problem.
The Problem:
Now that I have the problem modeled via the RabbitMQ framework, I need those "Messages" that are "pushed" to each endpoint (mobile device) to actually be a "Push Notification" instead of the standard message that will arrive to that device.
How can I model my solution to accomplish that ?
Thanks in advance.
Upvotes: 11
Views: 8522
Reputation: 4269
RabbitMQ can't send out the push notification itself.
For each message consumed from the a RabbitMQ queue, the "Consumer" service needs to invoke whatever push notification backend/API you are using (e.g. Firebase, AWS, etc.) using their SDK.
Upvotes: 0