Asynchronous vs Request-Reply vs One Way

Definition of Asynchronous:

http://www.w3.org/TR/xmlp-scenarios/#DS17

"A sender sends a message asynchronously to a receiver expecting some response at a later time. The sender tags the request with an identifier allowing the response to be correlated with the originating request. The sender may also tag the message with an identifier for another service (other than the originating sender) which will be the recipient of the response. "


Definition of Fire and Forget (aka One Way Message, Request-Only)


http://www.w3.org/TR/xmlp-scenarios/#S1

"A sender wishes to send an unacknowledged message to a single receiver"

Under certain interpretations, the Fire and Forget is a subcase of Asynchronous - without callback.


Definition of Request-Reply

http://www.w3.org/TR/xmlp-scenarios/#S3

Unlike popular belief, Request-Reply doesn't necessarily means the reply is sent back in the same thread. One can have a Asynchronous Request-Reply scenario.

VETRO Pattern

VETRO is a mouth-filling term for:
- Validate
- Enrich
- Transform
- Route
- Operate

http://soa.sys-con.com/node/46170

"Operate" is mysterious.... someone believes it should be "Orchestrate"... I understand that "Operate" means "Invoke a remote Endpoint".

Anyway, as usual, patterns often create a Procustes' Bed of abstract definitions draining away energies from a free independent analysis of reality.

(Theseus kills Procustes)

A Pattern Language

Amazon link

I highly recommend this book, full of original insights on Urban Planning, Anthropology and Mass Psychology.

On a general level, this article is a general presentation on the "pattern language" topic.

Enterprise Integration Patterns

I have bought the PAPER book, so I can read it in the park...

http://www.eaipatterns.com/

by Gregor Hohpe

I really love this book, it's an endless source of inspiration.
Germans really excel at classification, they are braniacs!
We Italians excel at fantasy instead.

Here http://camel.apache.org/enterprise-integration-patterns.html a very good list of these patterns and how to use them.

I would like to share some very meaningful phrases:

"The solution is not the first approach that comes in mind, but one that has evolved through actual use over time" (preface).