Red Hat OpenShift Cloud Functions

Subtitle
Bringing serverless capabilities to Red Hat OpenShift

Red Hat OpenShift Cloud Functions

Overview

Main Content

Red Hat OpenShift Cloud Functions brings serverless capabilities to Red Hat OpenShift, enabling event-driven architectures with a consistent Kubernetes-based operational model. These serverless capabilities help organizations become more agile while providing a more efficient use of computing resources.

Additional Content

Serverless architectures have emerged as a natural evolution of modern application development, and additionally provide for integration with classic and pre-existing applications.

 

 

Serverless is an architectural model that provides an event-driven way to implement distributed applications that can auto-scale on demand. Because the execution of these applications (functions) is driven by events, overall resource consumption can be reduced which can result in cost savings.  Red Hat’s vision is to create an integrated portfolio of Red Hat Middleware products, acting both as event sources for functions and the destination of service calls from functions.

OpenShift can run on any cloud, and your serverless infrastructure can, too. With OpenShift Cloud Functions, you can now have function portability across any cloud, whether public or private.

A core tenet of modern application development is to eschew corporate standards in favor of using the right runtime for the job, which means that polyglot development environments are a necessity. Your serverless infrastructure should support multiple runtimes, and Red Hat OpenShift Cloud Functions supports developers in implementing polyglot functions using Java, Python and Node.js (JavaScript). Or, if another runtime or language is required, a Linux container can be executed as the function.

Concepts

  • Function or Action - An ephemeral piece of code that runs in response to an event.

  • Trigger - Class of events that can happen to start an action.

  • Rule - An association between a trigger and an action.

  • Sequence - Orchestration of a group of functions

  • Package - Bundle a set of actions, feeds and rules.

  • Feeds - A stream of events that start Triggers through polling, webhooks, etc.

Use Cases

Including serverless functions in application architectures is recommended when portions of workloads require asynchronous, concurrent and parallelizable units of work. Alternatively, when portions of the workload are infrequent, on-demand, and have unpredictable scale, architectures including serverless functions may also be warranted.

Here is a list of some of the most common use cases for functions as as service (FaaS):
 

  • Processing web hooks

  • Scheduled tasks (similar to cron jobs)

  • Data transformation

  • Image manipulation (compression, conversion, and so on)

  • Speech-to-Text conversion

  • Mobile video analysis (frame-grabbing, object-detection)

  • Mobile/MBaaS /single-page apps

  • PDF generation

  • Chat bots

  • Much more...


If you want to try OpenShift Cloud Functions for yourself, completely in-browser with no installation or signup required, visit learn.openshift.com/serverless

Build Something Today

Let's walk through everything you need to build your first application.

Get Started