Before deploying event-driven messaging infrastructure, platform engineers must carefully evaluate system workloads, performance requirements, and deployment regions. This concept topic explores how to select appropriate cloud providers, choose right-sized Service Classes, and automate the lifecycle management of Event Broker Services through the Cloud Console.
Selecting Cloud Providers and Regions
Deploying messaging infrastructure in SAP Integration Suite, advanced event mesh requires careful architectural planning before triggering automated provisioning workflows. Administrators must align the messaging infrastructure with expected application workloads, performance requirements, and regulatory boundaries.
The platform offers full deployment flexibility across major public cloud hyperscalers, such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP), as well as Dedicated Regions deployed on-premises or within private cloud data centers. Choosing the optimal cloud region is driven by three primary operational considerations:
- Geographic Proximity and Latency
Co-locating Event Broker Services in the same cloud region as primary event producers (such as SAP S/4HANA Cloud instances or core microservices) drastically reduces round-trip network latency, accelerating real-time message processing.
- Data Transfer Costs
Minimizing cross-region and cross-cloud traffic lowers egress bandwidth fees, keeping enterprise integration costs predictable.
- Regulatory Compliance and Data Sovereignty
Certain legal frameworks require sensitive operational data and message payload spools to remain strictly within specific geographical boundaries.
Customer-Controlled Regions extend Cloud Console management into private data centers to enforce compliance without sacrificing cloud-native administrative workflows.

Service Sizing and Service Classes
Service Classes define the hardware allocation, compute capabilities, and capacity boundaries of an Event Broker Service. Administrators select a Service Class based on four core performance metrics:
- Concurrent Client Connections
The total number of simultaneous applications, IoT devices, or integration endpoints connected to the broker.
- Message Throughput
The maximum volume of incoming and outgoing messages the service must process per second.
- Message Spool Storage
Dedicated persistent disk capacity allocated for holding unacknowledged or queued messages during consumer offline periods.
- Redundancy Requirements
Non-production testing environments utilize standalone developer tiers to conserve costs, whereas production environments require high-availability enterprise tiers operating across multiple availability zones.
Automated Provisioning and Lifecycle Management
Once service parameters are selected, administrators launch provisioning directly from the Cloud Console. The platform automates underlying infrastructure orchestration, provisions dedicated messaging nodes, applies default security profiles, and assigns distinct connection endpoints for supported protocols including AMQP, MQTT, REST, and Solace Web Messaging. Post-deployment, administrators manage running instances throughout their lifecycle, scaling spool storage dynamically, upgrading Service Classes to handle application growth, applying zero-downtime platform updates, or decommissioning inactive instances to release cloud resources.
