REST API Design Examples: Checkpoint Recaps

REST API Design Examples: Checkpoint Recaps

TipBroker Bex, Messaging and broker domain expertCheckpoint: Resource Modeling

You now know:

  • A 500-thermostat fleet reporting every 30 seconds produces about 16.67 requests per second.
  • Keeping resources as nouns lets GET, PUT, and query filters carry the action without inventing verb-style URLs.
  • The same hierarchy can return current readings, setpoints, history, and clean 404 Not Found errors without changing the API shape.

TipBroker Bex, Messaging and broker domain expertCheckpoint: Offline Devices

You now know:

  • A tracker can be considered offline after 180 seconds without heartbeat, but that does not make the resource disappear.
  • 200 OK fits cached location plus connectivity metadata; 404 is for unknown vehicles or missing data.
  • 503 Service Unavailable is reserved for cases where the service cannot fulfill the request and should usually include retry guidance.

TipBroker Bex, Messaging and broker domain expertCheckpoint: Status and Protocol Choices

You now know:

  • 201 Created belongs to successful device registration, while 200 OK belongs to successful reads or cached stale data.
  • For the explicit minimal-header CoAP/UDP/IPv4/Ethernet example, 46 of 50 counted bytes are headers (92%); actual frames may include options, security, and more link overhead.
  • CoAP fits constrained request-response sensors; MQTT fits publish-subscribe monitoring; HTTP is useful but expensive for tiny battery messages.

Technical boundaries. The checkpoints use a fleet average, a chosen heartbeat threshold, and an explicitly minimal packet example to explain API decisions and communication costs. Their figures stop describing the same case when reporting differs from 500 thermostats every 30 seconds, offline detection differs from 180 seconds, or packet counting includes options, security, and additional link overhead.

Back to the chapter