APPENDIX

DETAILED FEATURE COMPARISON

BROKER AND UNIVERSAL
MESSAGING EDITIONS

1 | © 2015 Software AG. All rights reserved. For internal use only
UM EDITIONS: CLIENT APIS (SLIDE 1 OF 2)

Client API Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
JMS
JNDI †
Java ‡
C++ ‡
C# .Net ‡
Python  
Excel VBA  
JavaScript  
Adobe Flex  
Microsoft Silverlight  
† Server can act as a JNDI provider
‡ UM and Broker APIs are not compatible with each other
2 |
UM EDITIONS: CLIENT APIS (SLIDE 2 OF 2)

Client API Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
iOS  
Android  
AMQP (1.0)   †
MQTT (3.1.1)   †
Integration Server “JMS” ‡
Integration Server “Native pub/sub” §
REST  
SOAP  

† Requires a 3rd party client library

‡ Except pub.jms:sendBatch service
§ Version 9.7 and higher. Migration utility available 9.8 and higher.

3 |
UM EDITIONS: TRANSPORT PROTOCOLS

Transport Protocol Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Sockets (Unicast) †
Sockets with SSL †
HTTP  
HTTPS  
Multicast  
IPC (shared memory)  
RDMA (remote shared memory)
 

† UM and Broker clients/servers are not interoperable

4 |
UM EDITIONS: AUTHENTICATION/AUTHORIZATION

Auth. Feature Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Client-provided ID †
Basic auth (user/password)
Client cert auth
Per channel pub/sub ACL
Admin ACL
Group Based Permissions  §

† Client provides an identifier that controls what functions are permitted

§ Ability to administer the server based on groups rather than individuals. UM provides ‘Security
Groups’ that permit inherited permissions to be granted based on security group membership.
5 |
UM EDITIONS: ADMINISTRATION

Administration Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Java API †
C++ API  
C# .Net API  
Google Protobuf Support  ‡
User Interface MWS Portlets Enterprise Manager §
Command Central ¶

† UM and Broker admin clients are not compatible with each other
‡ UM natively supports the use of google protobuf message payloads in all native languages. This is
exposed in Integration Server in 9.7 and higher.
§ Enterprise Manager: a rich stand-alone Java GUI for administering any number of UM instances
¶ UM Command Central support is more comprehensive for UM than for Broker
6 |
UM EDITIONS: HIGH AVAILABILITY

HA Feature Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Active-active clustering NUMWS
 add-on only
†

Active-passive clustering ‡
Policy-based clustering
  §
(multi-send policy)

† True server-side active-active clustering for full redundancy without 3rd party dependencies.
‡ Requires shared storage and 3rd party clustering software, e.g. Windows Cluster, Veritas,
Serviceguard, or similar.
§ Provides client-based alternative for true active-active clustering, but with significant caveats
relating to performance and duplicate handling. Is not planned to be implemented in UM as UM
offers true active-active clustering.

7 |
UM EDITIONS: MESSAGE ROUTING

Routing Feature Broker NUMWI & NUMWF & NUMTF Notes

NUMWS
Server-to-server forwarding Territories & Zones & Channel Zones, Joins and Federated
†
Gateways Joins Namespace

Remote-control subscriptions
Admin API  Data Groups ‡

User Subject Based Routing  Subscriber name filtering §

Direct Delivery  Data Stream Delivery ¶
Advanced Selectors Extensions to SQL 92 type
  selectors
Ф

† All allow selective server-to-server message forwarding based on type, metadata or content. Zones is UM equivalent for Territories and is available in 9.8 release.
‡ UM provides additional pub/sub resources (DataGroups) that enable subscriptions to be managed by back end processes instead of end-clients. Similar but more
limited capabilities are available in Broker through the Admin API.
§ UM can direct messages to specific users by setting a subscriber name in the message.
¶ Each connection in UM can be assigned a DataStream which can be directly written to by any permissioned user, without needing a channel, topic, queue,
datagroup or the Admin API.
Ф UM provides support for advanced selector syntax such as Time & Distance enabling greater flexibility for content routing. Not yet available through Integration
Server.
Note: None of the features marked ‡, §, ¶ and Ф are yet available through Integration Server.
8 |
UM EDITIONS: QUALITY OF SERVICE (SLIDE 1 OF 2)

QoS Feature Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Transient  †
Simple  ‡
Volatile/Reliable §
Guaranteed/ Persistent ¶

Determined per message Ф

(JMS)
per channel/
Time-to-Live per channel
message
per channel/ message

† Messages stored in memory only if there are active subscribers.

‡ Messages stored in memory. Message lost and sequence number reset on restart.
§ Messages stored in memory. Message lost, but sequence number continued on restart.
¶ Messages stored on disk and guaranteed not to be lost on failure or restart.
Ф Quality of service can be configured on a per-message basis
9 |
UM EDITIONS: QUALITY OF SERVICE (SLIDE 2 OF 2)

Administration Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Off-heap topics/queues  
Capacity  †
Priority async only async only ‡
Message Replay  §
Conflation  ¶

† Ability to limit the capacity of a channel and discard messages when the capacity is exceeded.
‡ IS JMS triggers currently uses sync subscription, so cannot use UM priority messaging. This
may change in a future release.
§ Available through UM API.
¶ Merging of multiple partial events. Available through UM API.

10 |
UM EDITIONS: PLUGINS

Plugin Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Web Proxy   †
Simple Web Server   ‡
Servlet   §

† Server can act as a pass-through web proxy

‡ Server can act as a simple web server
§ Server can act as a servlet container

11 |
UM EDITIONS: MONITORING & DEPLOYMENT

Plugin Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
Monitoring: Optimize for
†
Infrastructure
Deployment: Deployer ‡

† UM is monitorable by Optimize for Infrastructure from 9.5 onwards

‡ Deployer supports UM from 9.5 onwards

12 |
UM EDITIONS: PERFORMANCE – (SLIDE 1 OF 2)

Performance Attribute Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
JMS persistent 1kB messages X X*4 X*4 †
JMS persistent 10kB messages
Y Y*3 Y*3 †

JMS persistent 100kB messages

Z Z*2 Z*2 †

Large Number of Concurrent

<10K >100K >100K ‡
Connections

† This is a very simple JMS test using Integration Server: one publisher, one subscriber.
Do NOT expect similar differences in real-life scenarios, although you can expect UM to be at least
as fast as Broker in a like-for-like configuration

‡ UM is proven to scale above 100K concurrent connections whilst maintaining a consistent

throughput of 100,000 messages a second and latency of <1ms per message.

13 |
UM EDITIONS: PERFORMANCE – (SLIDE 2 OF 2)

Performance Attribute Broker NUMWI & NUMWF & Notes

NUMWS NUMTF
High Update Rate / Low Latency
(Unicast)
 <2ms <2ms †

High Update Rate / Low Latency

(Multicast)
  <50μs ‡

High Update Rate / Low Latency (IPC)

  <4μs §

High Update Rate / Low Latency

(RDMA)
  <6μs ¶

† For a sustained throughput of 250,000 messages a second with 5,000 concurrent connected users, each consuming 50
messages a second, UM is proven to deliver latency of <2ms average.
Broker cannot handle this volume of messages.
‡ UM supports multicast delivery enabling extremely low latencies of 50 microseconds for delivery to 5000 concurrently
connected clients. Broker does not support multicast
§UM supports shared memory communication for the lowest possible latency when clients are on the same machine as the
UM server. Broker does not support IPC.
¶ UM supports remote shared memory communication for the lowest possible latency across a suitable (Infiniband) network.
Broker does not support RDMA.
14 |
15 | © 2015 Software AG. All rights reserved.