CPS1 Evolves into a Unified Platform Orchestrator with a Cloud Development Environment

We are very excited to announce the latest news and innovations in the new version of the Cloud Programming Shell (CPS1)! 🎉

TL;DR: CPS1 has evolved to become a unified Platform Orchestrator integrated with a Cloud Development Environment (CDE).

Now, CPS1 is capable of provisioning cloud service infrastructure in a way that is unified with the environment where the developer actually writes, tests, and executes the application code. Unlike any other solution on the market, in CPS1, the application and infrastructure are treated as a single unit.

Core Concepts of CPS1

CPS1 is based on four fundamental concepts: Workspaces, Resources, Templates, and Environments.

• Workspaces: This is where the developer connects their IDE to write, run, and test code. Developers access a standardized environment with all the necessary tools already configured.
• Resources: These are the external dependencies the application uses to function, such as databases, queues, and caches.
• Templates: The configuration that defines how an Environment should be provisioned. It contains the definitions for Workspaces and Resources required for the developer to work in a complete and isolated manner.
• Environments: The practical result of provisioning the Workspaces and Resources defined within a Template.

For more details on these concepts, visit the CPS1 Key Concepts page in our official documentation.

Unified Workflow Demonstration

In the video below, we demonstrate the creation of a complete Environment for developing a NodeJS application. See how simple and unified the process is:

• Template Creation: We define the nodeapp-aurora template.
• External Resource: We add an Aurora PostgreSQL resource, which is automatically provisioned on AWS.
• Local Resource: We add a Redis resource, provisioned internally within the Kubernetes cluster where CPS1 is installed.
• Workspace Configuration: We define the development environment with the required NodeJS version, Git repository, and the application's execution port.
• Provisioning and Access: We provision the Environment and access the Web IDE instantly, with everything ready to start developing.

Infrastructure Orchestration

The idea of using Kubernetes to orchestrate infrastructure outside the cluster has been gaining significant market adoption. This approach offers several advantages, such as the automated reconciliation between the desired infrastructure state and the real world, powered by Kubernetes operator control loops.

Furthermore, it enables the creation of a single workflow for both applications and infrastructure. This drastically reduces the need to integrate multiple tools, simplifying processes and decreasing technical complexity.

In contrast to projects like kro (Kube Resource Orchestrator) and Crossplane, CPS1 stands out for being much simpler to adopt and implement.

New Catalog

At CPS1, we embrace a "batteries-included" philosophy: we believe it is essential to provide a solid starting point for platform engineers while ensuring that CPS1 remains easy to customize.

The catalog is the set of Packages, Resources, and Templates installed on your instance. This new version brings out-of-the-box support for:

• AWS SNS
• AWS RDS Aurora MySQL
• AWS RDS PostgreSQL
• AWS OpenSearch

To learn more, check out our Helm Chart cps1-catalog.

You can install and start using CPS1 for free right now. Check out our Quickstart Guide to get started.

Check the full documentation: https://docs.cps1.tech