Understanding under the hood implementation of Message Subscription

Hey There,

I was just wondering how the Message Subscription Model of Backendless works.Is it just the mechanism of Network Polling wrapped under the hood (Because I saw this “pollingInterval” parameter somewhere in the docs) , or it has some built in Real-time mechanisms like that of Firebase ?
And , similarly , do the Push Notifications of Messaging API too work on Polling System , or are there any other implementations )
(P.S I am too sensitive about polling system just for Networking and data costs, so want to know which pattern should i follow :slight_smile:

Hi Pujan,

Currently (that is in version 3.0.8 of Backendless) message retrieval in our publish/subscribe system is based on polling. That is the client sends periodic requests to the server to grab any pending messages. In one of the future version (in the near future) we will provide an option to developers to choose between poll vs push for the pub/sub messages.

The push notification system is different from publish/subscribe. With push notifications, messages are delivered through Google/Apple/Microsoft servers and arrive to the devices without any polling.

Regards,
Mark