Search…
Vamp Concepts
Release Agent
Integrations
Applications
Conceptually, an application in Vamp is a collection of microservices that shares a single Kubernetes Namespace.
At Vamp, we strongly believe Development, Test, Acceptance, and Production (DTAP) is incompatible with microservice-based application development. We maintain that the Testing and Acceptance steps should be done on real user traffic in Production to validate new features and optimize the business value of software. This is why we recommend reordering DTAP to DPAT.
Vamp provides all the tools and features you need to start testing safely in production. However, you can still use Vamp to manage your DTAP environments.
Vamp enables you to release across multiple Kubernetes clusters and multiple cloud providers. In this context, an application is a unique combination of a Kubernetes cluster and a Namespace name.
The Vamp definition of an application differs slightly from the Kubernetes definition of an application.
Kubernetes characterizes an application as a single workload plus configuration data.
Common Scenarios
DTAP (Development, Test, Acceptance, and Production) is a traditional way of splitting up your environments and is strongly linked to monolithic application development.
In Vamp, your Development, Test, Acceptance, and Production environments are different applications, possibly with the Development, Test and Acceptance applications sharing one cluster, and Production using a separate cluster. The different applications typically share the same microservices, but with different versions, and need to be updated sequentially.
Multi-region Production is what happens when, for performance or legal reasons, you run the same microservices in different data centers. This approach is increasingly popular as a response to regulations such as the EU General Data Protection Regulation (GDPR) and California Consumer Protection Act (CCPA).
In Vamp, each production environment is an application using a different cluster, typically running in different cloud provider regions.
Regional, Multi-Tenant SaaS is where you allow your customers to select which geographical region and, in some cases, which cloud provider they want you to use for supplying your service to them.
In Vamp, each region is an application in a running in different clusters and using different cloud provider regions.
Regional, Single-Tenant SaaS is where you allow your customers to select which geographical region and, in some cases, which cloud provider they want you to use for suppling your service to them and you use a different environment for each customer.
In Vamp, each customer is an application, potentially running in different clusters and using different cloud provider regions. The different applications are clones that use the same microservices.
Last modified 3mo ago
Copy link
Contents
Common Scenarios