Device Administration Service - Pub-Sub
About This Architecture
Event-driven device administration service using OCI Pub-Sub with dual-topic architecture for decoupled control and configuration flows. The input_device_service publishes control events to the control_data topic while config_service manages favorites via the favorites_topic, both consumed by subscribe_handler and favorites_cache_subscriber for real-time synchronization. This pub-sub pattern eliminates tight coupling between device services and administration clients, enabling independent scaling and fault isolation. Fork this diagram on Diagrams.so to customize topic schemas, add dead-letter queues, or integrate additional subscribers for audit logging or analytics. The dual-cache strategy (favorites_cache) with bidirectional feedback loops ensures eventual consistency across distributed device administration clients.
People also ask
How do I design a scalable device administration system using OCI Pub-Sub with separate control and configuration topics?
This diagram shows a pub-sub architecture where input_device_service and config_service publish to separate topics (control_data and favorites_topic), decoupling publishers from consumers. The subscribe_handler and favorites_cache_subscriber process events independently, with favorites_cache providing eventual consistency across DAS Clients while maintaining bidirectional feedback loops.
- Domain:
- Cloud Oci
- Audience:
- OCI solutions architects designing event-driven device management systems
Generated by Diagrams.so — AI architecture diagram generator with native Draw.io output. Fork this diagram, remix it, or download as .drawio, PNG, or SVG.