The “things” service takes care of persisting Things and Features.
Model
The model of the things service is defined around the entities Thing and Feature:
Signals
Other services can communicate with the things service via:
- ThingCommands: implementing classes provide commands which are processed by this service
- ThingEvents: implementing classes represent events which are emitted when entities managed by this service were modified
Persistence
The things service uses Pekko persistence and with that Event sourcing in order to persist changes to and restore persisted things.
Enforcement
The things service enforces/authorizes thing signals by the via policyId referenced
policy.