High & Low Water Marks
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
The high and low water marks on the client message queues allow you to alert and/or take mitigating steps, should a client’s queue reach or breach either. For example, you may impose a throttle on the number of messages sent to a client, if the high water mark is breached. Once a throttle is on and the low water mark is breached, you may ease or remove the throttle. Such techniques will ensure each end user will get the best possible experience from your application. See Best Message Delivery for more info on this.
