Architecture

Where Prodvana Fits

Prodvana is a control plane for coordinating applications that run on cloud resources such as GKE or EKS. Prodvana consists of an agent that runs on your cluster that is used to manage the applications that are deployed. The agent is a consistent interface for the underlying resource substrate this allows a uniform experience for users using the Prodana interface.

37523752

Prodvana Network Architecture

Architecture

Prodvana is an interface between your Application and Infrastructure/Platform layers. Each Prodvana Instance is isolated from all other customers and has its own instance of application, UI, and agent servers.

This architecture describes how the internal instance of Prodavna works for a customer.

Prodavna's APIs at the Infrastructure layer allow you to plug in existing components that are exposed to Application teams in a managed way.

44804480

Prodvana's architecture stack

Architecture Layers in Detail

Prodvana Application Management UI

The application management interface provides a UI and CLI to interface with managing your application. At this layer you can script the CLI in scripts and use the

Prodvana Application Management API

There is a gRPC and REST API to access the resources that build the Application Management UI and CLI tooling. The layer above is composed entirely of these APIs and does not use internal functions inaccessible to customers.

This layer allows you to manage external resources such as databases, queues, etc that you wish to expose to your Application.

Prodvana Infrastructure API and Interface

This interface combines conventions as well as APIs to manage external resources you wish to make available to the management API.

Integrations here consist of systems such as Kubernetes, Docker Registries, and other control flow resources such as ticketing systems.

📘

Differences between Infrastructure and Application Resource Linking

Infrastructure resources that are linked are globally exposed to all applications while Application resources are specific to the application.

Architecture Benefits

By utilizing a separation of concerns approach there are three key benefits that are outlined in the next section.

  • Velocity
  • Ownership
  • Modularity & Composability