Feature Support in PubSub+ Messaging APIs

The different APIs all support common functionality that is essential for messaging. These APIs evolve over time to meet use-case requirements for client applications, therefore there are slight differences in feature support.

The PubSub+ Messaging API for iOS is a mobile API. For the list of features supported for the iOS API, see iOS API.

Here's a summary of the current support for features; you can use this summary as a comparison to select the messaging API that's right for your requirements. API- or platform-specific features are described on the individual Messaging API pages. The following table shows:

  • A minimum event broker version where required, otherwise the feature is available in all supported event broker versions.
  • A minimum API version where required, otherwise feature support for each API is indicated using the following symbols:
    • Supported—A green check with no version number beneath it indicates that the feature is available in all supported API versions.
    • —A gray cross indicates that this feature is not currently supported.
    • —A gray dash indicates that this feature cannot be supported due to technical limitations in the API.
Feature C .NET JavaRTO JCSMP Java JMS JavaScript Node.js Python Go

Direct and Guaranteed Messaging Support

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Request and Reply Messaging

 

Supported

Supported

Supported

Supported

Supported

1.1+

Supported

Supported

Supported

Supported

Structured Data Types (SDTs) that Don't Rely on a Specific Architecture or Programming Language

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Logging and Customizing through Property Parameters

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Local Transactions

 

Supported

Supported

Supported

Supported

Supported

Supported

1.4+

XA Transactions

 

Supported

PubSub+ Cache Client Support

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

1.6+

Durable Endpoint Provisioning

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Use Selectors

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Message Compression Support

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

OAuth 2.0 Authentication

event broker version 9.12+

Supported

7.21+

Supported

10.16+

Supported

7.21+

Supported

10.13+

Supported

1.1+

Supported

10.13+

Supported

10.9+

Supported

10.9+

Supported

1.3+

Supported

OAuth Token Refresh

event broker version 10.1+

Supported

7.24+

Supported

10.19+

Supported

10.3+

Supported

10.16+

Supported

1.1+

Supported

10.10+

Supported

10.10+

Supported

1.5+

Supported

1.2+

Kerberos Authentication

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

1.2+

Supported

Distributed Tracing (Context Propagation)

event broker version 10.2+

Supported

10.21+

Supported

10.17+

Supported

10.17+

Supported

10.15+

Supported

10.15+

Replay

event broker version 9.9+

Supported

7.18+

Supported

10.12+

Supported

7.18+

Supported

10.11+

Supported

Supported

10.7+

Supported

10.7+

Supported

1.2+

Supported

Delayed Redelivery

event broker version 10.3+

Supported

10.18+

Supported

10.18+

Topic Dispatch

 

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Negative Acknowledgments (NACKs)

event broker version 10.2+

Supported

7.26+

Supported

10.21+

Supported

10.5+

Supported

10.17+

Supported

1.4+

Supported

10.15+

Supported

10.15+

Queue Browsing

 

Supported

Supported

Supported

Supported

Supported

1.2+

Supported

Supported

Supported

Partitioned Queues

event broker version 10.4+

Supported

7.25+

Supported

10.20+

Supported

10.4+

Supported

10.19+

Supported

1.3+

Supported

10.19+

Supported

10.13+

Supported

10.13+

Supported

1.5+

Supported

1.3+

Feature C .NET JavaRTO JCSMP Java JMS JavaScript Node.js Python Go

For Java, Node.js, Go, Python, and JavaScript APIs, the Durable Endpoint Provisioning feature is implemented using the Missing Resource Strategy.

  • For the Node.js and JavaScript APIs—On consumer start, the Missing Resource Strategy defines the action to take when an endpoint does not exist.
  • For Python, Java, and Go APIs—On receiver start, the Missing Resource Strategy defines the action to take when an endpoint does not exist.
  • For the JavaScript API—To provision queues or topic endpoints on the broker requires version 1.8 of the API or later.

The use of the Missing Resource Strategy also means that you cannot deprovision the endpoints.

Support for Distributed Tracing (Context Propagation)

Context propagation with PubSub+ Messaging APIs is supported by the Solace PubSub+ OpenTelemetry API Libraries. These libraries allow you to inject context into or extract context from PubSub+ event messages.

You deploy the PubSub+ OpenTelemetry API Libraries alongside the PubSub+ Messaging API for the programming language you are using to develop your application. These libraries have dependencies on the OpenTelemetry API (which must also be deployed with your application). For information about the compatibility of the PubSub+ OpenTelemetry API Libraries, PubSub+ Messaging APIs and required dependencies, see Distributed Tracing Version Compatibility.

The PubSub+ OpenTelemetry API Libraries support only W3C propagators.

For information about specific libraries and where to get them, see:

Support for Queue Browsing

Client applications can use the PubSub+ Messaging API to look at Guaranteed messages spooled for a queue in the order of oldest to newest without consuming them. For more information about using queue browsing for:

Support for Partitioned Queues

Partitioned queues allow you to easily scale the number of consumer applications in your event mesh. PubSub+ event brokers ensure that all related events are delivered to the same consumer in the correct sequence and can re-balance the event stream when you add or remove consumers.

Support for Negative Acknowledgments

Consumer applications can send an acknowledgment (ACK) or a negative acknowledgment (Nack) based on the settlement outcome of processing a guaranteed message. Rather than send an explicit acknowledgment (Ack) (as described in Feature Support in PubSub+ Messaging APIs), you can signal (via a settle method/function) a settlement outcome to the event broker. For more information about using Nacks for: