| ID | product.device_management.registry_service |
|---|---|
| Description | Source of truth for devices and their state. |
| Key | registry_service |
| Type | microservice:service |
| Status | active |
| Team | Device Management |
| Owner | device-mgmt@iotgateway.example |
| Technologies | Go, PostgreSQL, gRPC |
| Tags |
Table of contents
Attributes
| api_style | REST + gRPC |
|---|---|
| rps | 8k |
Guide
Device Registry
The Device Registry answers the question every other service eventually asks: “is this a real, active device, and what is its current state?” It owns the device record, the certificate that proves a device’s identity, and the twin — the desired vs reported state of each device.
Why a single source of truth
Ingestion, OTA and the dashboards all need a consistent answer about a device. Centralising identity and twin state here keeps those answers authoritative and auditable instead of scattered across services.