Lifecycle policy for Solace products, allows users to prepare for end-of-life product transitions. Milestones and phases from Product Introduction through to End of Support are defined with reasonable timeframes for each phase.
Lifecycle Policy for 3230, 3260, 3530-01, 3560-01 and SolCache can be found here.
To learn about support services for Solace PubSub+ Products, see our Support page.
For a list of the support dates for specific versions of Solace PubSub+ software products and SolOS firmware, see Support Dates for Release Versions.
The Product Lifecycle Policy, which applies to the product as a whole, is illustrated in the diagram below.
Note that support for certain versions of SolOS firmware and certain versions of PubSub+ software products follow different timelines as described in Solace Support Services. For a list of these versions and their support dates, see Support Dates for Release Versions.
Descriptions of each stage in Solace’s Product Lifecycle are presented in the following table.
|Milestone / Phase||Description|
|Product Introduction||Marks the beginning of the General Availability phase. At this point customers may begin to purchase the product.|
|General Availability||During this phase customers may purchase the product without restriction. Customers with current support plans will receive Major, Maintenance and Hotfix releases applicable to the product.
The General Availability phase typically lasts 3 to 4 years.
|End of Sales||Marks the end of the General Availability phase, and the beginning of the No New Sales Phase.|
|No New Sales||During this phase the product is not generally available for purchase. Customers with current support plans will receive the same level of support as during the General Availability Phase.
The No New Sales phase is 5 years long.
|End of Support||After 5 years of No New Sales, customers will no longer have the option of renewing their support plans, and Solace will cease providing support for the product.|
The Support dates for the Solace Products are provided in the table below.
|End of Sales|
|End of Sales |
|End of Support
|CHS-3530AC-02-A||December 1, 2021||December 1, 2026|
|CHS-3560AC-03-A||December 1, 2021||December 1, 2026|
|CHS-3560AC-06-A||December 1, 2021||December 1, 2026|
The Solace Queue Management System (QMS) is supported for 5 years from the date of sale.
This section lists the deprecated features in the Solace PubSub+ Platform.
|Name||Description||Recommended Alternative(s)||Final Version||Removal Date|
|Cut-Through Persistence (CTP)||CTP, also known as Cut-through Messaging, enables the delivery of guaranteed messages with very low latency from Solace PubSub+ to consumers with relatively low message rates and a small number of clients, but it limits the use of many of the newer features of PubSub+ event brokers. Please type “show message-spool stats” and check that ||Guaranteed messaging||April, 2022||May 31, 2022|
|Solace PubSub+ Messaging API for C support for Solaris/SunOS||Solace will stop providing builds for Solaris/SunOS after the next scheduled release of the C API. |
The following build packages will no longer be distributed:
• SunOS 10 i386
• IPC for SunOS 10 i386
• SunOS 10 x86_64
• IPC for SunOS 10 x86_64
• SunOS 10 Sparc 32-bit
• IPC for SunOS 10 Sparc 32-bit
• SunOS 10 Sparc 64-bit
• IPC for SunOS 10 Sparc 64-bit
|N/A||Release 7.23.0 available in September, 2022||June, 2026|
|PubSub+ Event Broker Services deployed in VM-Based Regions||Solace will no longer be offering event broker versions in PubSub+ Cloud that can be deployed in VM-based regions. Instead, broker version releases can only be deployed in Kubernetes. Existing event brokers services deployed in VM-based regions must be migrated to Kubernetes and this impacts Public Regions, Dedicated Regions, and Customer-Controlled Regions.||Migrate event broker services to use Kubernetes.||10.0.1||September 30, 2024|
Note: Formal notifications of a product reaching any product lifecycle milestone will be sent by email to customers on active Support Plans. Contact Solace Support at firstname.lastname@example.org to be included in these notifications.