Features
- Best Message Delivery
- Bi-Directional
- Cascading Transport Layer
- Client Connectivity (Roundtrip Monitor)
- Client Driven Events
- Compression
- Conflation
- Firewall Compatible
- Guaranteed Message Delivery
- Hierarchical Topics
- High & Low Water Marks
- High Performance & Scalability
- Multiple Queue Types
- Multiple Message Types
- Multiple Transport Layers
- Secure
- Simple & Flexible API
- Technology Agnostic
- Topic Aliasing
- Web Sockets
- Zero Copy
- Zero Download
- Zero Fan Out Time
- Zero Latency
Conflation can be switched on to ensure that each end user/client gets the best possible experience when using your application.
By switching conflation on, if a given attribute/entity changes two or more times before the messages are read by the client application, then only the most recent value is sent, hence preventing the client application from having to process/read the stale data. This is a fairly important technique when deploying applications with high data volatility such as trading or betting platforms, where the prices of a single security can be changing over eight times a second.
For example, on a web based FX trading platform, where the price of a single product (currency pair) can be rapidly changing, the end user may be trading GBP/USD. If the price displayed on their screen is not the most recent tradable price, they face two problems. The first is the end user goes to trade the price and their trade is rejected, as the price is no longer ‘good’. Secondly and more inportantly, end users notice that your price is always n seconds/milliseconds slow and start to arbitrage you based on a more accurate/up to date third party price feed. Obviously the latter is emphasised where a client is an algorithmic/automated trading program rather than a human being.
