the interaction between the Content Enricher and the data source is by definition synchronous (the Content Enricher cannot send the enriched message until the data source returns the requested data), a synchronous protocol (e.g., HTTP or an ODBC connection to a database) may result in better performance than using asynchronous messaging. The Content Enricher and the data source are inherently tightly coupled, so achieving loose coupling through Message Channels (60) is not as important.
