Within the IT industry, we're seeing a steady shift from an RPC (remote
procedure call) integration style to asynchronous, document-based
integration. More and more developers are realizing that asynchronous
services are core to a new, loosely coupled and message-driven architecture.
In practice, while most developers and architects I work with are sold on the
value of an asynchronous architecture, it introduces a steep learning curve
that makes it more difficult for them to take the next step. Having seen the
good, the bad, and the ugly sides of many integration projects, I'll try here
to pass on some experiences on the benefits, common hurdles, and best
practices of implementing asynchronous services and the systems that support
them.
The main benefits that are enabled by asynchronous services and the
associated loosely coupled, message-based architecture are:
Re... (more)