Considering performance in the domain

When you design your broker domain, and the resources associated with its components, there are several areas where decisions that you make can affect the performance of your brokers and applications:

Message flows
A message flow includes an input node that receives a message from an application over a particular protocol (for example WebSphere MQ).

You need to consider how you split your business logic; how much work should the application do, and how much should the message flow do? Every interaction between an application and a message flow involves I/O and message parsing and therefore adds to processing time. Design your message flows, and design or restructure you applications, to minimize these interactions.

For more information about these factors, see Optimizing message flow response times.

Messages
The type, format, and size of the messages that are processed can have a significant effect on the performance of a message flow. For example, if you process persistent messages, these have to be stored for safekeeping.

For more information about these factors, see Optimizing message flow response times

Broker configuration and domain topology
You can configure your broker domain to include multiple brokers, multiple systems, multiple execution groups, and so on. These can play a part in how message flows perform, and how efficiently messages can be processed.

For more information about these factors, see Optimizing message flow throughput and Performance considerations for Real-time transport.

All these factors are examined in more detail in the Designing for Performance SupportPac (IP04).

For a description of common performance scenarios, review Resolving problems with performance.

For further articles about WebSphere Event Broker and performance, review these sources:

Related concepts
Performance considerations for Real-time transport
Related tasks
Optimizing message flow throughput
Optimizing message flow response times
Resolving problems with performance