Device Administration Service - Pub-Sub

OCIArchitectureintermediate
Device Administration Service - Pub-Sub — OCI architecture diagram

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.

OCIpub-subevent-drivendevice-managementmicroservicesdistributed-systems
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.

Generate your own architecture diagram →

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.

Device Administration Service - Pub-Sub

OCIintermediatepub-subevent-drivendevice-managementmicroservicesdistributed-systems
Domain: Cloud OciAudience: OCI solutions architects designing event-driven device management systems
0 views0 favoritesPublic

Created by

May 7, 2026

Updated

May 7, 2026 at 5:51 AM

Type

architecture

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI