Google Cloud Messaging
summary
Google Cloud Messaging claims 400% growth since C2DM deprecation and hits over 200,000 requests/sec; it supports HTTP for multicast and a new XMPP endpoint for streaming (4,000 msgs/sec per connection, up to 10 connections → 40,000 msgs/sec). Messages use JSON with 4 KB payload, TTL and delay_while_idle, and downstream ACK/NACKs. Devices can send upstream messaging (4 KB, 20 queued sends, server must ACK or messages replay; 100 stored per project/device). New notification key groups up to 10 registration IDs per user; GCM moves into Google Play Services (FroYo+).
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:08Google Cloud Messaging
- 1:50What is Google Cloud Messaging
- 3:43Time to Live
- 4:35Multiple Senders
- 5:03Message Multicast
- 7:03Search Server
- 7:34GCM
- 8:26XMPP
- 9:23Streaming
- 9:38Messages
- 10:45upstream messaging
- 14:10no connection
- 14:47message identifier
- 15:16knowledge message
- 15:36safe store
- 16:10Knology
- 16:49Knowledge
- 17:14Smart things
- 18:12GCM Framework
- 19:15Registration
- 21:56Message Delivery
- 23:19HTTP Endpoint
- 24:11Notification Key
- 25:25Optimization
- 26:06NotificationKey
- 27:14Outro
related talks
54mAndroid chat app in the cloud
52mIoT on Google Cloud Platform
50mWeathering the Cloud Storm: Building Resilient Geo-Distributed Apps
45mIoT at Google Cloud
40mMaking every minute count: How Nimses scales it's mobile platform on Google Cloud
01h 00mKeynote
39mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and Compliance
06mTop 5 Google Cloud announcements