Dedicated Cloud vs. BYOC
Redpanda offers two ways to provision clusters in the cloud:
- Dedicated Cloud
- Bring Your Own Cloud (BYOC)
Both methods offer the following features:
- Single-zone or multi-zone availability
- A single-zone cluster is deployed in one availability zone. If that availability zone fails, the cluster becomes unavailable.
- A multi-zone cluster is deployed across three availability zones, which provides higher resiliency in the event of a failure in one of the zones.
- Private networking using VPC peering
- Ability to export metrics to a 3rd-party monitoring system
- Managed connectors
- Unlimited retention with Tiered Storage
The following architecture diagram illustrates the relationship between the Redpanda Cloud (the control plane) and a VPC in AWS.
With the Dedicated Cloud, you host your data in Redpanda’s Virtual Private Cloud (VPC), and Redpanda handles provisioning, operations, monitoring, and maintenance. Redpanda also performs automatic backups to S3 (for AWS) or GCS (for GCP).
Dedicated clusters are single-tenant deployments launched from the Redpanda control plane. The Redpanda cluster is created in Redpanda’s VPC, and the endpoints are exposed so you can produce or consume events.
When you choose BYOC, you deploy Redpanda in your own VPC, so that all data is contained in your own environment. There is no outbound connection from your VPC to the Redpanda VPC in the control or data path, which provides an additional layer of security and isolation.
Redpanda handles provisioning, operations, monitoring, and maintenance. You can choose AWS or GCP as your cloud provider.
Setting up a BYOC cluster is initiated from the Redpanda control plane. This is a two-step process:
- You bootstrap a Virtual Machine (VM) in your VPC. This VM spins up the agent and the required infrastructure.
- The agent communicates with the control plane to pull the control commands.