What I learned about IBM integration technology today

Even though I work for an IBM business partner, I am from a non-technical background so the variety of integration technology options in the IBM portfolio is really quite bewildering.

Today, I got the most succint explanation ever on when to use Message Broker and when to use the Advanced Edition of IBM BPM (formerly, known as process server).

Here it is:

  • Message Broker is asynchronous and stateless.
  • Process Server is synchronous and stateful.

Both can do the opposite but that’s what they were made for.

Full Disclosure: I work for anĀ Axispoint Solutions Ltd, an IBM business partner. The opinions in this piece are my own.

2 comments for “What I learned about IBM integration technology today

  1. seanblezard
    November 23, 2011 at 10:09 pm

    Hi, it does get murky. The old WPS tended to fit into the high-volume system-centric BPM space eg processing credit card transactions with human involvement only by exception. MQ is a message broker that tends to be used to asychronously de-couple systems or to facade other IBM technology. I think 7.5 represents the start of a shake-up, the lines between the heritage Lombardi stack and the IBM WPS stack are getting very blurry.. Especially since both share the same runtime now in 7.5.

  2. Anonymous
    November 24, 2011 at 11:16 pm

    Sean – Being Lombardi-heritage, I completely agree that 7.5 is the start of the confusionSeeing quite a few situations where an MQ client is looking for human-centric BPM and understanding if there is a business case for advanced v standard edition is not always transparent (even in complex integration situations).

Leave a Reply

Your email address will not be published. Required fields are marked *