Term | Definition |
---|---|
Agnostic | |
API | See Application Programming Interface |
CEP | Complex Event Processing |
Cloud | |
Container | |
DELETE | |
Docker | The name of ___________ |
GET | |
HW | Hardware |
IoT | Internet of Things |
IIoT | Industrial Internet of Things |
Java | |
Meta data | |
Microservices | |
MQTT | |
MSA | See Microservice Architecture |
Nanoservice | Smaller segment than a microservice. Very fine-grained service where the service's overhead outweighs its utility. __________ uses microservices and does NOT use nanoservices. |
North Side | |
PaaS | See Platform as a Service |
Platform as a Service | A cloud-based environment in which to develop, run, test, and maintain web-based applications. The PaaS environment provides the entire IT resource stack as a service and provides all of the facilities required to support the complete life cycle of building and delivering web-based applications. Using PaaS enables the creation and deployment of web-based application software without the cost and complexity of buying and managing underlying hardware, operating software, and utilities. Using PaaS therefore enables Developers to accelerate the pace of developing applications while reducing the complexity because Developers can provision, deploy, and manage applications using one unified management system. By using PaaS, Developers get their application to market faster, and can innovate and experiment with new technologies using existing public, private, or hybrid cloud infrastructures. |
PLC | Programmable Logic Controller |
Polyglot | |
POST | |
PUT | |
REST | short for RESTful |
RESTful | Representational State Transfer, or RESTful web services. Use REST with ________. |
Rules Engine | And why is a rules engine important to IoT edge systems? A rules engine is a software system that is connected to a collection of data (either database or data stream). The rules engine examines various elements of the data and monitors the date, and then triggers some action based on the results of the monitoring of the data it. Basically, a rules engine is a collection of "If-Then" conditional statements. The "IFIf" sets the condition and informs the rules engine what data to look at and what ranges or values of data must match in order to trigger the "Then" part of the statement. The conditional portion of the statements inform , which then informs the rules engine of what action to take or what external resource to call on, when a matching the data element is foundis a match to the "If" statement. Most rules engine engines can be dynamically programmed - meaning that is new if/then new "If-Then" statements or rules can be provided while the engine is running. The rules are often defined by some type of rule language with simple syntax so as to allow enable non-programmers Developers to provide the new rules. Rules engines are one of the simplest forms of "edge analytics" provided in IoT systems. They allow Rules engines enable data picked up by IoT sensors to be monitored and acted upon (actuated). Typically the actuation is accomplished on another IoT device or sensor. For example, a temperature sensor in an equipment enclosure may be monitored by a rules engine to detect when the temperature is getting too warm (or too cold) for safe or optimum operation of the equipment. The rules engine, upon detecting temperatures outside of an the acceptable range, would cause shuts off the equipment in the enclosure to be shut off. |
SaaS | See Software as a Service |
SDK | See Software Development Kit |
Service-Oriented Architecture | |
Snappy | The name of ____________ |
SOA | See Service-Oriented Architecture |
Software as a Service | |
Software Development Kit | |
South Side | |
SW | Software |
UI | User Interface |
...