Prodvana has core concepts that the platform is built upon. These concepts are exposed as gRPC and REST APIs to allow easy integration into existing workflows and tooling.
This is organized from the point of view of a developer starting the application or product they are managing.
The application scope is a collection of Services and Capabilities that are dependent on one another in a way that fulfills a business's need. The application defines the context and management policies for its constituent pieces based on its business requirements. Within an application, there are release channels where services live.
Release channels are a single deployment target. Service instances are materialized with a configuration acceptable to the release channel.
Services are the underlying components of an application. Most applications will have multiple services communicating with each other and other systems.
Integrations are 3rd party systems you wish to use in control flows for managing your application. Examples are monitoring and observability systems, docker registries, ticketing systems, etc.
Protections validate that Applications, Release Channels, Services, and Runtimes are in acceptable states before and after release.
Runtimes are where services you create are run. Examples are Kubernetes clusters, serverless systems, or other job-running frameworks. Runtimes are linked to your Prodvana account and are managed by you. Runtimes support extensions that increase their functionality and usefulness to the platform. Example extensions include cost, service meshes, and security scanning.
Updated 19 days ago