One Framework, Cloud to Edge
Architecture at a Glance
Your solution can include an application running on edge devices and a cloud-side application for operators, dashboards or system integrations.
You build the application behavior and customer experience:
- Your Edge Application handles your domain logic, such as reading equipment data or running AI inference.
- Your Cloud Application provides the interface and workflows your customers need.
WEDA connects these parts through a shared management framework:
- WEDA Core coordinates management from the cloud.
- WEDA Node carries out device-side operations and reports information back.
Use WEDA Console, WEDA's management UI, or build your own interface through the APIs.
Components and Responsibilities
The diagram separates the applications you build from WEDA's runtime components and development resources.
| Component | Role in your solution |
|---|---|
| WEDA Cloud | Provides centralized management through WEDA Core. WEDA Console gives operators a UI, while APIs let your applications integrate management capabilities. |
| WEDA Edge | Provides the device-side environment. WEDA Node connects the device to WEDA Core and supports local workload execution and reporting. |
| Cloud API & Enablers | Help you build cloud-side applications and integrate WEDA with your existing systems. |
| Edge Enablers | Help your edge application connect field equipment and sensors, for example through WEDA SubNode. |
| Advantech Container Catalog (ACC) | Supplies Ready-to-use applications and Ready-to-develop projects that you build for your target hardware. |
ACC supports application development and preparation. It is not a communication step between WEDA Cloud and WEDA Edge.
How WEDA Cloud and Edge Work Together
WEDA Core maintains the configuration you want a device to use, while WEDA Node applies that configuration on the device and reports its state back. You define changes through WEDA Console or your own application using WEDA Core APIs.
This coordination uses the Digital Twin Protocol shown in the architecture diagram. The Device Shadow represents two views of the device's state:
- Desired state: The configuration you want the device to use.
- Reported state: The state the device last reported.
WEDA features show the state reported by the device, such as the runtime status of deployed containers, so you can check whether a requested change has taken effect.
Alongside state synchronization, WEDA Node sends device telemetry to WEDA Core, where your applications can access it through the Data Engine.
A Custom Device sends data to WEDA Cloud without WEDA Node. Its data is also available as DataStreams through the Data Engine.
Where Developers Extend WEDA
Your Cloud Application
Your cloud application connects to WEDA Core through its APIs. Use them to:
- Build a customer portal.
- Visualize device data.
- Integrate device management into an existing system.
WEDA Console provides a management UI you can use alongside your own application.
Your Edge Application
Your edge application runs your domain logic on the device, such as collecting equipment data or performing AI inference.
Use WEDA SubNode to integrate peripheral devices and sensors. WEDA SubNode reports their data through WEDA Node.
Advantech Container Catalog (ACC)
ACC offers Ready-to-use applications and Ready-to-develop projects. Build a Ready-to-develop project before you deploy it.
Once your application is prepared, use WEDA's container deployment capabilities to deliver it to target devices.
WEDA provides the surrounding management capabilities for devices, applications, models and data.