Edge is a lightweight Internet of Things middleware that connects embedded
devices, gathering data and providing application interfaces to your device
IoT Framework - Edge
You can use Edge IoT as a service or as an on-premise platform. Deploying Edge
is trivial, requiring a very lightweight server setup.
The Edge IoT Framework enables your Internet of Things, easily. Edge is a middleware platform that allows bidirectional device-to-cloud communication: simple device values, set-points, unstructured data and more. Edge enables your web applications and connected devices to be in sync, simplifying the complexity of M2M communication. Edge is data agnostic, in other words it’s completely transparent to the meaning of the data or contents that are exchanged. It manages how data are gathered, stored and delivered. Through its API, any client (device or web application) can access any Edge device information, data values, controls, alarms, for any business logic purposes.
There are many interesting features found in Edge IoT: it’s secure, extendable and lightweight.
Agile and Solid
Edge is secure because it implements solid authentication protocols and strategies that are fine-tuned based on user driven use cases and domain partitioned data.
Edge is either PaaS or on-premise: yes, you can deploy Edge easily in your own infrastructure to have full control of your cloud.
It’s lightweight and easy-to-deploy to allow great portability, especially in prototyping and testing environments.
Edge is extendable through script injection or building new containers that include the core packages.
Edge supports both relational and NoSQL Databases.
Edge API and Protocols
Edge is a middleware platform to connect devices and applications. To intergrate Edge in your ecosystem, a solid definition of API and supported protocols are needed. Edge provides three protocols for device communication: HTTP/HTTPS, MQTT and Websocket. This allows great flexibility for many different scenarios. HTTP is very simple, easy to integrate and largely adopted.
HTTP REST API are great when your web application needs to send and receive data from Edge. MQTT was designed to be extremely lightweight and useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
Websockets are very useful for “near” real-time, full-duplex communication.