← Back to the chapter · Previous detail

Technical detail · CoAP Observe: Efficiency and Lifecycle

Observe capacity, handshake cost and cache freshness

Deploying CoAP Observe requires capacity, security-setup and cached-response freshness measurements as well as notification counts.

Measure server memory per observer, a client registered for resource updates, and delivery delay under load. Direct server fan-out means sending to each registered recipient. No fixed subscriber count selects the protocol by itself. Compare MQTT, a publish/subscribe protocol using a routing service called a broker, when measurements show that direct delivery misses capacity or delivery targets.

Include security setup in the exchange budget. A fresh Datagram Transport Layer Security (DTLS) handshake, which establishes connection security state, can dominate a short exchange; its round trips and latency depend on version, authentication, loss, and link delay. Reuse an established session where appropriate or use supported resumption. Also choose Max-Age, the response’s freshness lifetime, to match the freshness requirement: a proxy, an intermediary acting for another endpoint, may reuse a cached response while fresh even if the physical temperature has changed.

← Back to the chapter · Previous detail