Reduce your memory usage with parsers and message trees

Every message flow uses parsers, and therefore they are integral to all message flows. Parsers construct a message tree from incoming data, in an Input node for example, and then serialize a bitstream from the message tree, for example in an Output node. When a message flow processes larger messages, the message tree can grow and use more memory than the bitstream itself.

Parsers are used to own the incoming message data, construct a message tree from that incoming data, and then serialize a bitstream from a message tree. When a message flow processes larger messages, the message tree can grow and use more memory than the bitstream itself.

The information in this guide is intended as a guide to not only reduce the memory usage of your current message flows, but also offer examples and good practices for planning and creating future flows.

The best practice information in the following sections share common approaches to solving common problems based on real customer environments. They do not provide a "one size fits all" solution. They assume that you have a basic understanding of IBM® Integration Bus. As technology evolves and improved functionality is added to the product, new recommendations and advice might be added to the information in these documents.