Conceptually, an application in Vamp is a collection of microservices that share a single Kubernetes Namespace.
At Vamp we strongly believe that DTAP is an anti-pattern combined with microservice-based application development &DevOPS. We believe 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. That’s why we recommend to reorder the traditional DTAP to DPAT. Vamp provides all the tools and features you need to start testing in production in a safe and meaningful way. If you want to use Vamp to manage your DTAP environments, then we won't stop you.
Vamp enables you to release across multiple Kubernetes, across multiple cloud providers, so in practical terms an application is a unique combination of a Kubernetes cluster and Namespace name.
DTAP stands for Development, Test, Acceptance, and Production. It's a traditional way of splitting up your environments that's been around for decades 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.
At Vamp we strongly believe that DTAP is incompatible with microservice-based application development but if you want to use Vamp to manage your DTAP environments, then we won't stop you.
Multi-region Production is what happens when for performance or legal reasons you run the same microservices in different data centers. This is 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 perhaps also which cloud provider they want you to use to supply 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 perhaps also which cloud provider they want you to use to supply your service to them and you use a different environment for each customer.
In Vamp, each customer is an application possibly running in different clusters and using different cloud provider regions. The different applications are clones that use same microservices.