Checkpoint: Payload Evidence

Checkpoint: Payload Evidence

animation
rest
app-protocols
TipBroker Bex, Messaging and broker domain expertCheckpoint: Payload Evidence

The payload section gives you the evidence a design review should keep:

  • You now know that the example JSON body is 64 bytes and the compact CBOR estimate is 28 bytes.
  • You now know that 64 - 28 = 36 bytes, or 56.25% smaller, is a payload-size claim first; it becomes an energy claim only when transmit airtime dominates the device budget.
  • You now know why the chapter recommends JSON for cloud APIs and debugging, CBOR for constrained CoAP payloads, and Protocol Buffers for high-volume systems with strong typing.

Back to the chapter