Summary
While the need to version a service is still to be debated, one aspect which we
all need to accept is that services need to be maintained in multiple variants to
satisfy multiple classes of consumers. Service request can be enhanced to include
additional information which will help providers to apply rules to route requests
to the appropriate class or variant of the service. While it is tricky to handle this
kind of routing using a trivial handler or interceptor-level, an ESB provides you
all the required design patterns and hooks to enforce content-based routing. Then
neither the service provider nor the service consumer needs to be aware of these
complexities. These design patterns and hooks are grouped under the broader
heading of EIP and the next chapter is going to look at them in greater depth, again
with working code samples.
Enterprise Integration
Patterns in ESB
By now you will appreciate the fact that integration is not simple. Now, how can you
make it manageable and/or repeatable and thus simplify integration? Haven't you
come across the same problem in traditional software engineering before?
How did you manage the problem then? Yes, I am referring to nothing else other
than Patterns.
Pages:
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400