When you create a Decodable account, you have the option of deploying Decodable using two different deployment models: Managed Cloud and Bring-Your-Own-Cloud (BYOC). The following table summarizes the differences between the two deployment options and when to use one vs the other.
|Decodable's control and data planes run in Decodable Cloud.||Decodable's data plane runs in your own Cloud infrastructure.|
- You want to get up and running fast
- You want zero infrastructure to manage
- Data must stay within your VPC
- You want to consume cloud service provider committed capacity
Decodable's Cloud architecture is split into two separate planes for high availability and security purposes. Where this architecture gets deployed depends on whether you create a Decodable account in Managed Cloud or in a BYOC deployment. See the Managed Cloud and BYOC for more information.
In a Managed Cloud deployment, Decodable is responsible for hosting all Decodable services. This means that both the control plane and data plane services are hosted by Decodable, and you are not responsible for creating and deploying the cloud infrastructure needed to host Decodable. This is the most straightforward and easiest way of deploying Decodable. All you need to do if you want to use this deployment method is create an account. See Set up a Decodable Account to get started.
Managed Cloud Overview Diagram
In a BYOC deployment, you own and manage the AWS Cloud account that the Decodable data plane gets provisioned to. With BYOC deployments, you operate in a shared responsibility model with Decodable where you are responsible for the AWS Cloud account and infrastructure and Decodable is responsible for the services running on that infrastructure.
If you would like to set up a BYOC deployment of Decodable, contact us.
BYOC Overview Diagram
Updated about 1 month ago