From a3b83723b17b5b5890d0aadd943476422579695a Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Mon, 27 May 2024 20:22:06 +0530 Subject: [PATCH] Unsuitable part removed --- docs/welcome/why-kubeedge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 64ad7bbcbf..08e9ee8a4e 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -37,7 +37,7 @@ KubeEdge is composed of these components: - **[MetaManager](./architecture/edge/metamanager):** the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite). - **[ServiceBus](./architecture/edge/servicebus)**: a HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge. - **[DeviceController](./architecture/cloud/device_controller)**: an extended kubernetes controller which manages devices so that the device metadata/status data can be synced between edge and cloud. -- **MQTT Broker**: A server that handles MQTT messages for efficient communication with IoT devices. + ## Architecture ![KubeEdge Architecture](/img/kubeedge_arch.png)