Java Reference
In-Depth Information
Figure 4.2. ActionBazaar ordering before MOM was introduced
In the synchronous communication model, the user waited for the shipment request sub-
mission to finish processing before an order was completed. The problem was that the B2B
connection was often slow or unreliable. In addition, Turtle's systems were much slower
and overloaded compared to ActionBazaar's servers. And sometimes Turtle's systems were
dependent on other third-party systems. As you can imagine, this resulted in some unhappy
customers!
The answer was to integrate all external vendor systems through asynchronous messaging.
Figure 4.3
shows how this works. In this model, a MOM is put between ActionBazaar's
and Turtle's systems. A message containing the shipment request is sent to the MOM asyn-
chronously. This message is stored by the MOM until Turtle's system receives and pro-
cesses the request at its own pace. In the meantime, the user is sent a confirmation of the
order as soon as a message is successfully sent to the MOM, which is typically an instant-
aneous process.
