Does Google IoT Core support HTTP compression?

Question

Using the HTTP protocol, is it possible to leverage of HTTP compression (i.e. Content-Encoding: gzip) in order to reduce the body size of a publishEvent, reducing the total cost of IoT core?

score 2 · Accepted Answer · answered Mar 06 '18 at 09:00

I've received a feedback by Google, this is an excerpt:

Cloud IoT supports receiving data on gzip compressed encoding in the REST devices API. Though this approach could save you some bandwidth usage from your devices to Google Cloud, sending compressed data will NOT reduce the total cost of Cloud IoT core. Cloud IoT will account for ingress data the uncompressed version of the data for billing.

class · Answer 2 · 2018-02-21T00:58:05.363

1

I tested setting the gzip header in the Node HTTP example and it continued to work for me so you should be able to do this. Also note that you can use MQTT, which is a binary protocol, which may also help to reduce network overhead.

Note that the actual payload itself as well as configuration change messages are binary data that can be compressed before sending over the wire.

edited Feb 21 '18 at 00:58

answered Feb 18 '18 at 10:19

class

8,621
29
30

Thanks, however it's not clear to me whether Goggle charges the message considering the compressed size or not. – maurocchi Feb 19 '18 at 13:50
Added update -- you can send compressed payloads because the data is binary. – class Feb 21 '18 at 00:58

Does Google IoT Core support HTTP compression?

2 Answers2