Glossary

Platform

(see Full Page)

development and runtime engine for the Enterprise Internet of Things

Code

(see Full Page)

use to implement a backend API necessary to make web, mobile and IoT apps all perform and integrate in a customizable way.

Service

(see Full Page)

short-lived microservices that is expected to complete in under 30 seconds.

Requires

(see Full Page)

can import a Library to a Code Service.

Libraries

(see Full Page)

reusable sets of code that can be imported by one or more code services.

Timers

(see Full Page)

provide a mechanism where a code service can be scheduled to execute at certain time intervals.

Triggers

(see Full Page)

a mechanism that tie an action to the invocation of a code service.

Messaging

(see Full Page)

publish and subscribe to events and data within the system using a simple topic.

MQTT

(see Full Page)

Message Queuing Telemetry Transport is a lightweight publish-subscribe messaging protocol.

Topic

(see Full Page)

to keep messages separated and organized in a path that can be looked up.

Collections

(see Full Page)

use to store different types of data in your IoT solution.

Adapters

(see Full Page)

a custom software component that is deployed on IoT Gateway

Deployment

(see Full Page)

allow for controlling what system assets will run on an edge.

Devices

(see Full Page)

machines that have access to data and API’s while communicating with your IoT Solution.

Edge

(see Full Page)

allow for executing your IoT solution on distributed compute like an IoT Gateway devices.

Roles

(see Full Page)

allow groups of users to see specific applications and perform certain actions with permissions.

Users

(see Full Page)

an account that belongs to a person with a valid email, specific permissions may be assigned to users

Authentication Override

(see Full Page)

override the default authentication mechanism for users with a custom one using a Code Service.

API

(see Full Page)

Tools that can be used to interact with the platform and its assets.

Console

(see Full Page)

the developer’s web interface into the ClearBlade platform.

System

(see Full Page)

represents a backend for the, web dashboard, IoT networks, etc. that need a common system of record.

Portal

(see Full Page)

a single instance of a web application with preconfigured integrations with the ClearBlade System to which it belongs. It is fully responsive, mobile-friendly, and customizable.

Datasource

(see Full Page)

a definition object that is registered with the portal and

a function that is responsible for interacting with third-party APIs, responding to various lifecycle methods, and notifying the portal when new data is available.

Widget

(see Full Page)

Parser

(see Full Page)

offers a mechanism for manipulating a Datasource’s output prior to its ingestion by a widget.

Plugin

(see Full Page)

a JavaScript file that can be loaded by a portal to extend the default list of widgets and datasources.

SDK

(see Full Page)

Software Development Kits are collections of software used to integrate applications with the platform.

CLI

(see Full Page)

Command-line Interface provides easy to use commands for interacting with the platform.

Long-Running Service

A Code Service configured with a longer lifecycle than a conventional microservice, typically running indefinitely and managed by the Developer Console