Finding the Compromise – the Adapter Framework - Applied SOA Patterns on the Oracle Platform - page 402

basic event, the events data should be transported to the decision support system
( DSS ) or online analytical processing ( OLAP ) applications. You can employ
these options for CDC, but you still need to do an analysis for a proper decision
and also bear in mind that some of these options are available in the Enterprise
Edition only.
• The XML message construction can be easily done by XDB constructs if you do
not have legacy of existing cursors and will build everything from scratch. Other-
wise, a custom construction utility would be more suitable; at least you will avoid
a lot of mistakes by simply following the existing query logic in cursors.
• Message delivery is also one of the benefits. Actually, standardization options
here can be seen purely from an SOA perspective. We need application/message
agnostic protocol and MEP. JMS and JMS/AQ is an optimal choice as we could
avoid implementation application-specific adapters and minimize the ABCS foot-
print in general. Of course, if your SOA infrastructure is completely based on the
data model, provided by the OEBS XML Gateway or Application adapter by de-
fault, and all consumers are happy with that, then you should go for this solution.
However, evaluate the complete Oracle AIA implementation as it could be the
best choice, especially with all the industry PIPs.
Tip
We mentioned this before and we would like to repeat it again—SOA doesn't have to be
expensive. On the contrary, based on so many technologies and standards, it allows us to
choose the optimal combination of tools and methods exactly according to our specifica-
tions and budget. We are not selling Oracle products, so we have no interest in offering
AIA, CDC, ODI, and GG when you do not really need them. Actually, we strive to share
the lessons we learned from our practical SOA implementation, based on Oracle tools.
Finally, what operations will we get after replacing the Adapter framework with this event
driven solution? Are there any significant benefits of this radical simplification? Let's start
from core NFRs:
• That's a really interesting point. Yes, it's inexpensive and easy to use, but what
about the performance? Although the company's name is fake, the following
numbers are real:
◦ 350,000 to 450,000 outbound messages monthly for all OEBS domains.
The number of inbound messages is roughly the same.
◦ Depending on the financial period, the daily rate can be up to 100,000
messages per day.