Choosing an application type

Kelvin supports various application flows for a wide variety of use cases. In this introductory page we will expose those application types as well as its details.

Kelvin Applications

Kelvin Applications are the default application type provided by the Kelvin tool.
These applications are meant for use cases where developers wish only to focus on the data-processing step, thus delegating the application's process, resources and lifecycle management to the Kelvin Core engine. In other words, they are the ideal application type for low-code, simple applications. In addition, developers may override the underlying process and methods to deal with more elaborate, detailed scenarios.

Kelvin Applications are written in python programming language.

More information on Kelvin Applications here.

Generic Applications

The Generic application type allows the developer to freely specify the behaviour of the application.
Unlike Kelvin Applications, where a lifecycle is guaranteed, Generic applications are configured from scratch using a Dockerfile. These applications are suited for servicing independent software or content within the Kelvin Ecosystem

More information on Generic Applications here.

Bridge Applications

Bridge applications facilitate the linking between external data sources, and the Kelvin's Broker. Leveraging the same engine as Kelvin Apps, Bridge Applications provide specific configurations a flexible tool set set to handle reading and writing from and into the Kelvin's Broker.

More information on Bridge Applications here.