Service Class Options for Event Broker Services
You must choose a service class when you create an event broker service in SAP Integration Suite, advanced event mesh. Each service class has limits, such as the number of connections, storage, queues, and more. Depending on your requirements, you may need to choose a larger service class to meet your current needs.
Event broker services are deployed on customer-dedicated software event brokers. This means that your event broker services are completely separated and isolated from other event broker services.
The tables below show the service classes and the most common service-level limits that you may be interested in. For detailed information about other limits, contact SAP.
Regardless of its service class, all event broker services allow you to create and access only one Message VPN. This Message VPN has a name derived from the event broker service name, using all lowercase letters and replacing spaces with hyphens. For example, an event broker service named "My Service" would have a message VPN named "my-service". You can rename the Message VPN for an event broker service. You may notice other Message VPNs listed in Broker Manager. These Message VPNs are either disabled or are not user accessible or configurable. For more information, see Viewing and Managing the Message VPN.
Unless specified on this page, all other limits correspond to the limits for the underlying software event broker as specified in the Service Class Properties table.
The posted limits in the tables below refer to the latest version supported on advanced event mesh. Event broker services utilize a varying number of internal topic subscriptions, clients, queues, and connections based on the configuration of these features:
- Config-Sync
- Clusters and event mesh (DMR)
- Disaster Recovery (DR) using Replication
- VPN Bridges
These internally created topic subscriptions, clients, queues, and connections draw from the posted limit numbers. For example, on a Broker 1K event broker service, if a configured feature consumes nine connections, then your event broker service would have another 991 connections available.
You can use Broker Manager to find the number of clients, topic subscriptions, queues, and connections that are consumed by the configuration of features on an event broker service. Note that the maximum number of connections shown in Broker Manager may not reflect the actual values enforced by the Message VPN for the event broker service class. For example, to find the number of clients that were created internally for an event broker service, select Clients > Solace Clients from the navigation bar in Broker Manager.
- With the appropriate account permissions, you can change the message spool size of an existing event broker service using the scalable message spool sizing feature. For more information, see Adding Scalable Message Spool Size to an Existing Event Broker Service.
- If you are reaching the maximum queue messages for an existing event broker service, you can request to upscale the queue messages. You can view the Max Queue Messages for the event broker service by selecting it in Cluster Manager and then selecting the Configuration tab. See Upgrading Event Broker Services or contact SAP.
-
The Message VPN of an event broker service enforces connectivity limits for the service. Message VPN limits may differ from those shown in Broker Manager, which shows limits for the underlying software event broker. The connectivity limits listed in the following tables take precedence over those shown in Broker Manager.
| Service Class | Underlying Software Event Broker Size | Client Connections | Default Message Spool Size (See Note Above) |
High Availability |
|---|---|---|---|---|
|
Broker 100 (Developer) |
1K |
100 |
25 GB |
No |
|
Broker 250 |
1K |
250 |
50 GB |
Yes |
|
Broker 1K |
1K |
1,000 |
200 GB |
Yes |
|
Broker 5K |
10K |
5,000 |
400 GB |
Yes |
|
Broker 10K |
10K |
10,000 |
600 GB |
Yes |
|
Broker 50K |
100K |
50,000 |
800 GB |
Yes |
|
Broker 100K |
100K |
100,000 |
1,000 GB |
Yes |
Service-Level Limits for Each Service Class
| Service Class | Maximum Message Size (MB) | Maximum Number of VPN Bridges |
Unique Local-Only Subscriptions | Unique Local and Remote Topic Subscriptions1 | Queue Topic Subscriptions | Combined Number of Queues and Topic Endpoints | Enterprise Client Connections (SMF, AMQP) | IoT Client Connections (MQTT, Web Messaging, REST Incoming) | Maximum Queue Messages | REST Delivery Points (RDP) | REST Consumers | REST Connections (Outgoing) | Maximum Kafka Bridge Profile | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Broker 100 (Developer) |
10 MB |
25 |
1,000 |
500,000 |
10,000 |
100 |
100 |
100 |
240 million |
200 | 600 | 1,000 |
Small Maximum of 10 Kafka bridges and 300 connections |
||
|
Broker 250 |
10 MB |
25 |
50,000 |
500,000 |
10,000 |
250 |
250 |
250 |
240 million |
200 | 600 | 1,000 |
Small Maximum of 10 Kafka bridges and 300 connections |
||
| Version 10.25.8.3179-18 and earlier |
Version 10.25.8.3179-20 and later |
||||||||||||||
|
Broker 1K |
10 MB | 30 MB | 25 |
100,000 |
500,000 |
10,000 |
1,000 |
1,000 |
1,000 |
240 million |
200 | 600 | 1,000 |
Small Maximum of 10 Kafka bridges and 300 connections |
|
|
Broker 5K |
30 MB |
500 |
250,000 |
500,000 |
50,000 |
5,000 |
5,000 |
5,000 |
3 billion |
500 | 1,500 | 7,500 |
Medium Maximum of 50 Kafka bridges and 2,000 connections |
||
|
Broker 10K |
30 MB |
500 |
500,000 |
500,000 |
50,000 |
10,000 |
10,000 |
10,000 |
3 billion |
500 | 1,500 | 7,500 |
Medium Maximum of 50 Kafka bridges and 2,000 connections |
||
|
Prior to Version: LTS 10.26.0.8894-14 Rolling 10.26.6.12130-13 |
After Version: LTS 10.26.0.8894-14 Rolling 10.26.6.12130-13 |
||||||||||||||
|
Broker 50K |
30 MB |
500 |
5,000 |
2,500,000 |
5,000,000 |
500,000 |
50,000 |
30,000 |
50,000 |
3 billion |
1,500 | 4,500 | 22,500 |
Medium Maximum of 50 Kafka bridges and 2,000 connections |
|
|
Broker 100K |
30 MB |
500 |
5,000 |
5,000,000 |
5,000,000 |
500,000 |
100,000 |
30,000 |
100,000 |
3 billion |
1,500 | 4,500 | 22,500 |
Medium Maximum of 50 Kafka bridges and 2,000 connections |
|
1 Remote subscriptions are those that the local node learns from the event mesh.
Service-Level Limits for Flows and Transactions
| Service Class | Outgoing Flows | Incoming Flows | Transacted Sessions | Transactions |
|---|---|---|---|---|
|
Broker 100 (Developer) |
100 |
100 |
100 |
500 |
|
Broker 250 |
250 |
250 |
500 |
2,500 |
|
Broker 1K |
1,000 |
1,000 |
1,000 |
5,000 |
|
Broker 5K |
5,000 |
5,000 |
5,000 |
25,000 |
|
Broker 10K |
10,000 |
10,000 |
10,000 |
50,000 |
|
Broker 50K |
50,000 |
50,000 |
10,000 |
50,000 |
|
Broker 100K |
100,000 |
100,000 |
10,000 |
50,000 |