Message Compression Characteristics
FioranoMQ provides message compression on a 'per message' as well as on 'per destination' basis. In 'per message' compression, clients can enable or disable compression for each message. In 'per destination' compression, all messages sent to a particular destination (topic or queue) are compressed.
Client applications can choose compression levels and strategies from Zlib specifications using public APIs.
The available options are:
- NO_COMPRESSION
- BEST_SPEED (fastest compression)
- BEST_COMPRESSION
- DEFAULT_COMPRESSION
There are ten possible compression levels (0-9) available, where BEST_SPEED is defined as 1 and BEST_COMPRESSION is defined as 9.
The possible values for the compression strategy are:
- FILTERED: Compression strategy best used for data consisting primarily of small values with random distribution. It enforces more Huffman coding and less string matching.
- HUFFMAN_ONLY:
- DEFAULT_STRATEGY: This uses a combination of the LZ77 method and Huffman coding.
Compression support provided helps a client application to decide on the optimum compression level and strategy by providing APIs to check compression ratios of messages sent and/or received.
Compression involves compressing only the payload of the message and not its JMS header. The same set of APIs can be used for message headers as well as message selectors, irrespective of whether message compression is enabled or not.
FioranoMQ's implementation allows users to plug in their proprietary compression implementation, which overrides the default implementation.