Thursday, December 13, 2007

Enterprise Integration Patterns on Messaging

Asynchronous messaging is fundamentally a pragmatic reaction to the problems of distributed systems. Sending a message does not require both systems to be up and ready at the same time. Furthermore, thinking about the communication in an asynchronous manner forces developers to recognize that working with a remote application is slower, which encourages design of components with high cohesion (lots of work locally) and low adhesion (selective work remotely).

...

How can I integrate multiple applications so that they work together and can exchange information?

 

Use Messaging to transfer data frequently, immediately, reliably, and asynchronously

An enterprise has multiple applications that are being built independently, with different languages and platforms. The enterprise needs to share data and processes in a responsive way. This is the problem that messaging addresses.

No comments: