Cloud Functions: when to use them

In this page you will find use case information on why and when to use Cloud Functions.

Real use cases for Cloud Functions

In the next sections we will offer a brief overview of possible use cases and explain why a Cloud Function would need to be integrated in your project. You can learn more about its characteristics in this introduction page.

When should you use a Cloud Function?

In some cases, in order to manipulate and provide functionalities that can handle persistent storage or strict security parameters, a UI Component will not be enough. This is when a Cloud Function will come into play.

A few examples could be:

  • Creating custom applications that handle operation logs, like Service Logbook, where maintenance notes and operator actions are captured by the frontend, but securely persisted by the Cloud Function within its isolated Document Store database.

  • Creating custom applications that handle the browsing of documents, such as in the case of Document Management, where users can store and consult useful documentation regarding the machine. This option uses the Object Storage for persistent storage of data.

  • Creating custom applications integrated with third party systems that the machine builder is already using: The Support Ticket Connector app provides an interface that can be interacted with from the IXON Portal so that the operators can monitor incoming tickets from there.

Via the use of the FunctionContext, you will be able to access some resources, configuration options, and also the Document Store or Object Storage.

When should you NOT use Cloud Functions?

Use UI Components without a Cloud Function when:

  • The work can be done entirely in the browser, with no secrets or shared state. A pure UI Component is simpler.

Use API integration when:

  • You want to write an automation script of some sort in a preferred programming language;
  • You need to call the API from another system that does not live within the IXON Cloud.

Examples

The Service Logbook is a complete reference app that uses a Cloud Function as the backend for a UI Component. It's a good place to see all of these characteristics applied to a realistic problem.