Skip to content

Commit 763733e

Browse files
Update overview-broker.md
1 parent 2e09408 commit 763733e

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/iot-operations/manage-mqtt-broker/overview-broker.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,12 @@ The MQTT broker underpins the messaging layer in IoT Operations and supports bot
2727

2828
## Architecture
2929

30-
The MQTT broker has four major components:
30+
The MQTT broker has two major layers:
3131

3232
- Stateless frontend layer.
3333
- Stateful and sharded backend layer.
34-
- Kubernetes operator.
35-
- Health manager.
3634

37-
The frontend layer handles client connections and requests and routes them to the backend. The backend layer partitions data by different keys, such as client ID for client sessions, and topic name for topic messages. It uses chain replication to replicate data within each partition. [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) manages custom resources lifecycle. Health manager facilitates failure handling and recovery of backend and frontend pods.
35+
The frontend layer handles client connections and requests and routes them to the backend. The backend layer partitions data by different keys, such as client ID for client sessions, and topic name for topic messages. It uses chain replication to replicate data within each partition.
3836

3937
The goals of the architecture are:
4038

0 commit comments

Comments
 (0)