Is GCM service reliable for large scale push notification?

可紊 提交于 2019-11-29 08:09:07

One notification can send only to 1000 devices (GCM limit).So you must split your array of devices. 50.000 users its ok for GCM.

Our application serve 100.000 users.

As case you can use airpush notification service: http://www.airpush.com/

I think that GCM is a good choice to use. It's reliable and using it helps to conserve battery and data usage since it piggybacks other Google services. All you need is Android 2.2 or later with the Google services installed, which means no Kindle Fire.

I do not think that GCM would have any problems handling the number of messages or devices that you gave.

If you use it you will still have to write your own server component to handle registrations and message sending. I wrote a blog post that describes how this works.

Some commercial services that handle the server component for you (as well as other things) are AirBop, UrbanAirship, and ClixAp. Parse is a commercial solution that (I believe) does not use GCM. As I noted in the comment above I helped create AirBop

Like others we struggle with GCM as well for some time. However we believe we have finally figured out the factors which affect the performance of GCM the most:

For fastest delivery of Notifications with least amount of jitter: 1. delay_while_idle - set to false 2. time_to_live - set to zero (but we have set to 30 for just in case) 3. Canonical IDs - Make sure Canonical IDs returned by GCM replace the old PushID in database 4. collapse_key - The most important factor - set it to random or TOD to avoid Google to throttle notifications

With these, our GCM is working satisfactorily. Good wishes, post if you still have issues.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!