Environment Architecture for Dedicated Region and Customer-Controlled Region Deployments

If you use Private Regions, effectively managing the assignment of the private region Datacenters in your estate to your environments is crucial for the success of your PubSub+ Cloud deployment.

You can use environments to structure your estate so that you deploy event broker services depending on their purpose. You could have an environment for development and testing of event broker services, and another environment for production deployment of the services. This configuration allows you to create and test your event broker service safely in a secluded Kubernetes cluster, and then clone the event broker services to your production environment when they are ready.

This document outlines our recommended practices for organizing and managing environments to ensure optimal performance, security isolation, and operational efficiency. It includes information on the following topics:

For more information about private region Datacenters, see Private Regions.

For more information about environments, see Creating and Managing Environments.

Designing Your Estate for Environments

You can create environments to suit any requirement you have, for example, you may require a both a development and production environment. For an example use case, see Using Environments to Manage Your Estate.

When creating environments for your estate with private regions, you must assign at least one private region Datacenter to each environment you create before you can deploy event broker services to the environment. When designing your environments, you can:

  • assign a private region Datacenter to only one environment

  • configure an environment to have multiple private region Datacenters

  • deploy event broker services to Datacenters assigned to environments

You can deploy a single or multiple datacenters to a cluster. Solace strongly recommends deploying only a single datacenter to each cluster. Having a single datacenter per cluster provides the following benefits:

  • Independent Maintenance: You can maintain each Datacenter separately, allowing for scheduled maintenance without affecting your other environments.

  • Enhanced Reliability: Issues in one environment are limited to the Datacenter for that environment, and won't impact your other environments.

  • Tailored Resources: Each environment can be sized appropriately for its specific workload

  • Simplified Compliance: You can provide flexibility in your non-production environments, while adhering to compliance requirements in your production environments.

When designing your environment architecture, you can request certain Datacenters be assigned to certain environments. You can also move Datacenters to different environments at a later date. For more information, see Assigning Datacenters to Environments.

Solace can help you create or migrate your estate to an environment-based architecture. For more information, see Getting Help With Your Environment Architecture.

Using Environments to Manage Your Estate

Environments can help you manage your estate by helping compartmentalize your processes and workflows. Let's assume your organization has the following resources requirements:

  • A development team located in one geographic area that creates and configures your event broker services.

  • A testing team located in another geographic area that tests new event broker services to ensure they interact with client applications in your private cloud according to the needs of your estate.

  • A production environment that straddles three different geographic regions, where you deploy production ready event broker services.

In your development environment you have a single, small Kubernetes cluster assigned as the Datacenter in the same geographic region as your development office. Your organization uses this datacenter exclusively for creating and configuring event broker services. The cluster provides your developers with the resources they require to create and configure the event broker services for the connectivity requirements of your estate, while isolating the event broker service from your production environment. After configuring an event broker service, your developers transfer them to a testing team located in another geographic area.

In your testing environment, you have another Kubernetes cluster assigned as the Datacenter. This cluster is the same geographic regions as your testing center, which is in a different location from your development office. The Datacenter also contains applications used in testing the configuration of your event broker services. Your testing teams clone event broker services created by your development team in the development environment into a datacenter in the testing environment. The testing team can test the event broker service configuration in their environment, using their tools, while being isolated from both the development and production environments.

Your production environment is where your live event broker services are deployed, along with other applications critical to your organization's success. It contains three large Kubernetes clusters as its Datacenters, one in each of the three regions where your organization is active: Asia, Europe, and North America. After your testing team certifies an event broker service as production ready, they clone it to each of the Datacenters in your production environment.

This process ensures that your event broker services and your estate are unaffected by your development cycle. During each step, your estate is protected by the segregation the environments provide. You can create, test, and deploy event broker services in a process that ensures your overall success.

Assigning Datacenters to Environments

The easiest way to assign a private region Datacenter to an environment, is to include the environment assignment when you request the Datacenter through the Private Regions tab in the Cloud Console. You can also use the Cloud Console to assign or move Datacenters to different environments at any time.

Perform the following to assign a new private region Datacenter to an environment:

  1. Create an environment.

  2. Request a new private region Datacenter and include the environment assignment in the request.

If your private region Datacenters already exist with or without an environment assignment, or you change your mind about the environment assignment for a Datacenter, you can move the Datacenter to a different environment.

Getting Help With Your Environment Architecture

Moving to an architecture based on multiple environments with multiple Datacenters requires careful planning. Once you have created your environments, and assigned Datacenters to them, you may need to recreate, or clone your existing event broker services to ensure they are in the correct environments.

For new customers, Solace can help with architecting your PubSub+ Cloud deployment using environments from the start. We can provide guidance in creating your environments and Datacenters assignments, ensuring the best outcomes for your estate.

For existing Dedicated Region and Customer-Controlled Region customers, Solace can help:

  • Design an environment architecture that aligns with your existing requirements.

  • Migrate your existing estate so your event broker services are properly placed in your Datacenters and environments so they align with your existing requirements.

If you require help in either scenario, contact Solace.