The Roost platform on-demand creates an ephemeral environment to test each and every change and release it to production in real-time. The platform completely eliminates the need to have shared and static environments for testing.

The Roost platform continuously scans source-code repositories and auto-discovers environment configuration and dependencies from all your favorite tools like: Kubernetes YMYL files, Docker files, Docker compose, Helm charts, Terraform files, AWS CloudFormation, etc.

LOGO-Kubernetes-223px

 

LOGO-docker-178.83px logo-docker-compose-noback

 

helm-horizontal-color

 

logo-makefile

 

logo-terraform

LOGO-cloud-formation

Figure 1. The Roost platform automatically scans source-code repositories and auto-discovers configuration files, artifacts and dependencies from all your favorite tools.

The Roost platform's proprietary scanning process automates your build, deploy and test configuration for each of your pull requests (PRs). The Roost platform also provides templates (YMLs) that automatically defines your infrastructure and can be part of your source code repositories. 

 

Due to the complex nature of applications there will be multiple definition files of the service. The Roost control plane helps define and manage these configurations and automatically saves them to the source code. The Roost platform can create Kubernetes or Docker-based environments on AWS, GCP, or Azure as displayed below.

Fig1-auto-discovery

Figure 2. The Roost platform can manage multiple configuration files
for multiple applications all within the control plane.

 

How the Roost platform works with IaC scripts like Terraform or AWS CloudFormation

Fig2-Roost-terraform-configuration

Figure 3. Roost uses infrastructure as code (IaC) components defined in Terraform or CloudFormation scripts ensuring that the environment is created the way it was originally architected.

If you already have your infrastructure as code (IaC) components defined in Terraform or AWS CloudFormation, Roost will ensure that your infrastructure is created the way it was defined. This way, you can create or use your cloud-native infrastructure to run your application on demand with every pull request.

Once the change has been merged, or testing has been completed, the Roost platform automatically tears down configuration of the environments and will gracefully destroy the environment ensuring cloud costs are no longer being consumed.

 

Banner Ad_Demo

Sudhir Jangir

About Sudhir Jangir

Sudhir is the CTO and Co-Founder of Roost. He has 20 years of experience developing enterprise applications and leading technology teams.

Please Share this Blog

You may find these blog posts of interest too.

How to use Event Framework for Complex Test Environments
How to use Event Framework for Complex Test Environments
August 29, 2022

With the increasing number of services in cloud-native applications and their dependence on various third-party applicat...

How to Create a Docker Image from Dockerfiles for Fast K8 Testing
How to Create a Docker Image from Dockerfiles for Fast K8 Testing
August 29, 2022

Build a Docker Image from Dockerfile Using Ephemeral Environments How to Work with a Docker Image A Dockerfile is essent...

Accelerate Software Delivery Releases - Eliminate Staging Environment
Accelerate Software Delivery Releases - Eliminate Staging Environment
August 29, 2022

Current Testing and Staging Processes are Slow & Cumbersome Current DevOps pipelines have multiple test environments...