โ† Back to the chapter

Technical detail ยท Cloud IoT Platforms

Managed Services Hide Ownership

29.9 Managed Services Hide Ownership

A managed service can provide sign-in, queues, storage, and alerts quickly. The team still needs to decide who owns access, data retention, schema changes, and support. Record those owners during the trial. A quick setup alone does not settle these choices.

The device and cloud need a shared contract. A device can use a certificate or key to identify itself. Its payload needs units, a timestamp, a version, and any fault flags. Rules send that payload to storage, a chart, or an alert. Test whether a stale value can replace a newer one, whether a duplicate changes the result twice, and whether a rejected message leaves a trace.

Record what can move to another service and what must be rebuilt. CloudEvents describes common fields for events, and OpenTelemetry can describe traces through a system. Parquet is a column-oriented file format for exported data. MQTT topics, payload schemas, event fields, traces, CSV or Parquet exports, and API contracts are easier to carry forward than private rule editors or hidden shadow logic. Name the rules, functions, dashboards, and alert routes that would need to be rebuilt or accepted as lock-in.

A queue can preserve data while the link is down. A cold-room alarm or pump shutdown may still need to work at the device or gateway during that outage. Record the offline window, how duplicates are handled, the last good state, and who can diagnose a broken route. Test the local safety path in the edge review.

โ† Back to the chapter