Skip to content

WebSphere Message Broker (WMB) Tips – Part 2 (Message Flow Performance)

by on January 12, 2012

Continuing with our Message Broker Tips, Part 2 (Performance) is just a brief posting that captures a few quick items to look at when designing or evaluating the performance of your message flows.  Future posts will offer a more broad view of performance related items as well as go more in-depth on these:

1.  Keep Number of Nodes to a minimum to reduce message trees and processing

2.  Avoid full parsing of messages when not necessary (it is common for people to use RCN to simply change the message domain, however doing this forces a full parsing of the message even if that is not what you were looking to do)

3.  Only use persistent messages when there is a true business requirement to do this.  A good example of when this is not necessary is when you are building an interface as synchronous request/reply (i.e. Providing a list of inventory to web users).  In this case, if the transaction fails, and end-user will typically re-submit request and it is not necessary to keep the stale message.  It is also important to keep file IO to a minimum (i.e. writing/reading from queues and files).  It may be better to store small pieces of data in local environment.

4.  Review while/for logic for redundant processing – Try to do as much of mappings and logic single instances of loops.

5.  In general, message processing is more efficient for many small messages, then one large batch file.  Splitting messages may be more efficient and also allow you to load balance between these smaller messages if applicable.



From → Integration

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: