Overview

About Runtimes

Runtimes is a StackSpot tool to easily integrate Cloud resources into Stacks, Templates, and Plugins.

You can create applications consuming resources in an abstract and easy-to-manage way. It is possible to do it without the business application deployment complex steps. Your team can have a reliable system that guarantees the Cloud resources you need, avoiding configuration errors in applications in production environments.

Main concepts

Runtimes

It is part of the StackSpot platform to reduce the complexity to execute an application, including everything you need to deploy it. There are two ways you can benefit from this:

• Runtime Systems: abstractions and APIs (not just HTTP/REST) that StackSpot's users can use it.
• Runtime Environments: all the computing resources used to run the software in an environment.

OAM

OAM (Open Application Model) is an open-source specification adopted by the Cloud Native Foundation (CNFC). It allows you to describe how your application will be implemented, configured, and managed. You need to use this specification to create your applications with StackSpot Runtimes.

Components

They represent the technology and the Cloud services configuration, including containers orchestration services, database, and/or cache. The components can define required or optional parameters, you can change them to modify the behavior of the component. This gives you control to do what you need.

The components needs to be defined by the Cloud team specialists (Enterprise Architect), using a specific IaC (Infrastructure as Code) like Terraform and Crossplane.

Application

It is the representation of software, which ensures part of the domain (or business) rules of the company. You can design, develop, and publish. In the StackSpot Runtimes context, the application represents a group of components, including the Cloud resources that executes the application software and necessary services such as databases and/or caching.

Environment

It is a set of computing resources, you can configure in a specific way to run an application (application) and the required Cloud services (components). Environments can already exist and you can import them to StackSpot, or they can be fully provisioned using Cloud components, for example in development, homologation, and/or production environments.

Target

This is the address of a specific Cloud resource, representing an EKS cluster that can run applications through deployments that already exist and are not provisioned like the other Components.

Deployment

Represents the publishing of an application to an environment, including timing (timestamp) and status (success, error).

Runtimes Usage

Runtimes accelerate application Cloud components adoption and ensure environments are provisioned with the most appropriate components in the Stacks. You don't need to spend time getting to know the infrastructure, it spares you time to focus on the team's creativity.

The benefits are:

• Manage Cloud components with StackSpot;
• For Cloud specialists: the components and configurations are used in the applications in the Stacks;
• For developers: facilitates access and the components usage available by the Cloud specialists.

See how Runtimes can help your team:

1. Platform/Ops Team:

• SRE: responsible for the initial setup, they define AWS accounts, Kubernetes clusters, and configurations with the Runtimes CD (continuous delivery).

info

Use StackSpot's website to complete the SRE journey, and the BYOR (Bring Your Own Runtimes)

• Platform Developer: creates Cloud resources: Packages, Components, and Revisions.

2. Application Developer Team:

• Application Developer: creates the applications and uses the Cloud resources provided by the Platform/Ops developers.

Check out how Runtimes manages Cloud resources for your team:

Next Steps

• Quickstart

• Create your package