Saturday, January 14, 2012

Claim check messaging pattern with Oracle OSB

• reduce the message size to ease a performance problem
• make sure the message size conforms the size limitation of the messaging system (e.g. 4 mb limit in the MQMQ)

When the messages are too big to be processed efficiently by web services / transformation, it's better to save some parts of the message in database before the processing and then enrich the result of the processing with the saved data from the database.

See also blogs compilation about messaging for integration:

Please share comment.

Source: Steve's blog

Hohpe's Enterprise Integration Patterns

The Definitive Guide to SOA: Oracle Service Bus

No comments: