You must choose a service class when you create an event broker service in
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 their most relevant service-level (or system) limits in PubSub+ Cloud. The limits for an event broker service class correspond to the limits for the underlying software event broker. For example, the limits for the Enterprise 5K service class are the same as the limits for the 10K software event broker. For detailed information about other limits, see the SolacePubSub_<version>_limits_and_alerts spreadsheet under the relevant broker version folder on the Solace Products website. To access these spreadsheets, you must be subscribed to PubSub+ Cloud and have an account. If you have issues accessing the Solace Products website, contact Solace.
Regardless of its service class, all event broker services allow you to create and access only one 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 PubSub+ Cloud. 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 an Enterprise 1K event broker service, if a configured feature consumes nine connections, then your event broker service would have another 99,991 connections available.
You can use PubSub+ 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. For example, to find the number of clients that were created internally for an event broker service, select Clients >
- With the appropriate account permissions, you can change the message spool size of an existing event broker service 10.0 or later using the scalable message spool sizing feature. For more information, see Adding Scalable Message Spool Size to an Existing Event Broker Service.
- Event broker services prior to version 10.5 may have queue message sizes smaller than those listed in the table below. If you are reaching the maximum queue messages for an existing event broker service, you can upgrade to 10.5.1 and then 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 in PubSub+ Cloud in PubSub+ Cloud or contact Solace.
- Standalone event broker services are available after you add them as a service class to your Service Limits. To use standalone event broker services, contact Solace or request a limit change.
| Service Class | Underlying Software Event Broker Size | Client Connections | Default Message Spool Size (See Note Above) |
High-Availability | |
|---|---|---|---|---|---|
| Version 10.6.1 and earlier | Version 10.7.1 and later | ||||
|
|
1K |
100 |
10 GB |
25 GB |
No |
|
Enterprise 250 |
1K |
250 |
25 GB |
50 GB |
Yes |
|
Enterprise 250 Standalone |
No |
||||
|
Enterprise 1K |
1K |
1000 |
50 GB |
200 GB |
Yes |
|
Enterprise 1K Standalone |
No |
||||
|
Enterprise 5K |
10K |
5000 |
200 GB |
400 GB |
Yes |
|
Enterprise 5K Standalone |
No |
||||
|
Enterprise 10K |
10K |
10,000 |
300 GB |
600 GB |
Yes |
|
Enterprise 10K Standalone |
No |
||||
|
Enterprise 50K |
100K |
50,000 |
500 GB |
800 GB |
Yes |
|
Enterprise 50K Standalone |
No |
||||
|
Enterprise 100K |
100K |
100,000 |
500 GB |
1000 GB |
Yes |
|
Enterprise 100K Standalone |
No |
||||
Service-Level Limits for Each Service Class
| Service Class | Maximum Message Size (MB) | Unique Subscriptions | Non-Unique Topic Subscriptions | Queue Topic Subscriptions (See Note Below) | Combined Number of Queues and Topic Endpoints | Enterprise Client Connections (SMF, AMQP) | IoT Client Connections (MQTT, Web Messaging, REST Incoming) | Maximum Queue Messages (as of 10.5) | Maximum Kafka Bridge Profile (as of 10.6) |
|---|---|---|---|---|---|---|---|---|---|
|
|
10 MB |
1000 |
1,000,000 |
10,000 |
100 |
100 |
100 |
240 million |
Small Maximum of 10 Kafka bridges, and 300 connections |
|
Enterprise 250 Enterprise 250 Standalone |
10 MB |
50,000 |
1,000,000 |
10,000 |
250 |
250 |
250 |
240 million |
Small Maximum of 10 Kafka bridges, and 300 connections |
|
Enterprise 1K
|
10 MB |
100,000 |
1,000,000 |
10,000 |
1000 |
1000 |
1000 |
240 million |
Small Maximum of 10 Kafka bridges, and 300 connections |
|
Enterprise 5K
|
30 MB |
250,000 |
1,000,000 |
50,000 |
5000 |
5000 |
5000 |
3 billion |
Medium Maximum of 50 Kafka bridges and 2000 connections |
|
Enterprise 10K
|
30 MB |
500,000 |
1,000,000 |
50,000 |
10,000 |
10,000 |
10,000 |
3 billion |
Medium Maximum of 50 Kafka bridges and 2000 connections |
|
Enterprise 50K
|
30 MB |
2,500,000 |
10,000,000 |
500,000 |
50,000 |
30,000 |
50,000 |
3 billion |
Medium Maximum of 50 Kafka bridges and 2000 connections |
|
Enterprise 100K
|
30 MB |
5,000,000 |
10,000,000 |
500,000 |
100,000 |
30,000 |
100,000 |
3 billion |
Medium Maximum of 50 Kafka bridges and 2000 connections |
Service-Level Limits for Flows and Transactions
| Service Class | Outgoing Flows | Incoming Flows | Transacted Sessions | Transactions |
|---|---|---|---|---|
|
|
100 |
100 |
100 |
500 |
|
Enterprise 250 Enterprise 250 Standalone |
250 |
250 |
500 |
2500 |
|
Enterprise 1K
|
1000 |
1000 |
1000 |
5000 |
|
Enterprise 5K
|
5000 |
5000 |
5000 |
25,000 |
|
Enterprise 10K
|
10,000 |
10,000 |
10,000 |
50,000 |
|
Enterprise 50K
|
50,000 |
50,000 |
10,000 |
50,000 |
|
Enterprise 100K
|
100,000 |
100,000 |
10,000 |
50,000 |
The current service class names map to these legacy names previously used in PubSub+ Cloud:
- Enterprise 250— Nano
- Enterprise 1K—Kilo
- Enterprise 5K—Mega
- Enterprise 10K—Giga
- Enterprise 50K—Tera 50K
- Enterprise 100K—Tera 100K