When you design a message flow, the flexibility and richness of the built-in nodes often means that there are several ways to achieve the processing and therefore the end results that you require. However, you can also find that these different solutions deliver different performance and, if this is an important consideration, you must design for performance as well as function.
There are two ways in which your applications can perceive performance:
There are several aspects that influence message flow response times. However, as you create and modify your message flow design to arrive at the best results that meet your specific business requirements, you must also consider the eventual complexity of the message flow. The most efficient message flows are not necessarily the easiest to understand and maintain; experiment with the solutions available to arrive at the best balance for your needs.
Several factors influence message flow response times:
Use as few nodes as possible in a message flow; every node that you include in the message flow increases the overhead in the broker. There is an upper limit to the number of nodes within a single flow. This limit is governed by system resources, particularly the stack size, and you might find that this is in the region of 200 nodes.
Related concepts
Message flows
Message flow application deployment
Related tasks
Configuring the broker domain
Optimizing message flow throughput
Designing a message flow
Using more than one input node
Creating a message flow
Defining message flow content
Editing configurable properties
Related reference
Built-in nodes
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00355_ |