The cloud provider you choose is entirely based on your requirements and often tied to the requirements of your event-driven architecture (EDA) and the connectivity of your client applications to the event broker services. Some connectivity requirements use a public cloud provider while others require a private cloud. Most enterprise customers choose a private cloud to meet more their client connectivity requirements.
For the public cloud option, Solace provides what we refer to as Public Regions. The cloud providers available for these public regions are AWS, Google Cloud, and Azure. Public Regions are ideal for client applications that connect to event broker services using the public Internet, has the least amount of set up required by you, and lets you quickly start using PubSub+ Cloud.
Solace also provides an option called a Private Cloud. Private Clouds are either deployments that you set up (called Customer-Controlled Regions), or Solace sets up for you (called Dedicated Regions). Typically, you use private networks (or private regions) when connectivity between the event broker services and client applications require private IP addresses rather than public Internet, or when you require a specific deployments option (such as on premises infrastructure or other cloud providers). If a private network is required, you can contact Solace to deploy PubSub+ Cloud. For more information about the options, supported cloud providers, and on-premise environments, see Deploying PubSub+ Cloud.
The following table summarizes the deployment options available when you create an event broker service:
- Cloud Provider—The cloud providers selection in Cluster Manager.
-
Deployment Type—The type of environment where the event broker services are deployed.
- Kubernetes—These types of deployments offer the most flexibility because there are more frequent broker versions releases. Choosing a Kubernetes deployment also gives you earlier access to features when compared to VM-based deployments. Customer-Controlled Regions and Dedicated Regions, Solace supports many Kubernetes environments. For more information, see Deployment Architecture for Kubernetes.
- VM-based—(Deprecated) These deployments utilize VM-based images to deploy event broker services. The creation of event broker services is not possible.
-
Deployment Ownership Model—The type of deployment and who is responsible for the connectivity and maintaining the deployment environment.
| Cloud Provider | Deployment Type | Deployment Ownership Model | Description |
|---|---|---|---|
|
Amazon Web Services |
Kubernetes, which uses Amazon Elastic Kubernetes Service (EKS) |
Public Region that offers public Internet connectivity |
You connect to event broker services from client applications via the public Internet. Multiple versions of event broker services are available in the account. Multiple regions throughout the world are available, but if you don't see a region you require, contact Solace. |
|
Microsoft Azure |
Kubernetes, which uses Azure Kubernetes Service (AKS) |
||
|
Google Cloud Platform (GCP) |
Kubernetes, which uses Google Kubernetes Engine (GKE) |
||
|
Private Cloud |
Kubernetes Note: VM-based deployments are available, but Solace recommends that you use Kubernetes when possible. |
Client applications can connect to event broker services from private networks, public Internet, or both. Multiple versions are available in an account. Private clouds are useful when you deploy PubSub+ Cloud to a private network. Private clouds have a full range for cloud and on-premises support. You must contact Solace to set this up for your PubSub+ Cloud account. It involves additional steps. To get started, contact Solace and review the information, see Deploying PubSub+ Cloud. |
|
|
Amazon Web Service VM-based architecture (Deprecated) |
VM-based |
Public Region that offers public Internet connectivity |
Support for VM-based deployments is now deprecated and version 10.0.1 was the last event broker release that supported deployments in VM-based regions. For more details, see the Deprecated Features list. (Deprecated) The creation of event broker service is no longer possible. You connect to event broker services from client applications via the public Internet. Typically, only one or two broker versions are available in the account. |
|
Microsoft Azure Service VM-based architecture (Deprecated) |
VM-based |