Support for large data volumes

How does FUSE supports large data volumes including large message sizes and high arrival rates?

FUSE Message Broker

There is no internal limit for message size in the FUSE Message Broker - the main limitation being the amount of available memory - and FUSE Message Broker has been tested with message sizes of several megabytes.

However, the recommended way to send very large messages is to use Blob Messages which implements an out of band transport for messages. Blob Messages allows for files to be hosted on external http/ftp sites if required and can support either direct publisher <-> subscriber communication or publisher -> broker/file server -> consumer messaging.

You can alternative use JMS Streams for large message transfer. A JMS Stream will chop the message into a configurable size for transfer.
There are limitations however, and JMS Streams works well with only topics - or a single consumer on a Queue.

FUSE Message Broker has been designed to cope with very high data volumes arriving at an individual broker.
Consideration has been taken on maximizing throughput - including:

To provide massive scalability we recommend you use FUSE Message Broker in a network configuration:

This allows for thousands of clients to be federated across WANS, as well as offering great horizontal scalability. For more information see here.

FUSE ESB

FUSE ESB is scalable, if the implementation is architected correctly we can scale to support any number of messages with the right combination of configuration and hardware. We also do not set a message size limit per se, but you will run into the limits of technology if you want to move very large message sizes or attachments through the bus. In short, we support large message volumes through a combination of tuning and scalability strategies allowing for load balancing among clusters of JBI containers. Very large message sizes or attachments can be made more performant through application

Labels

 
(None)