Databases Reference
In-Depth Information
Where the SOA Suite fits
You may have noticed that we have deliberately stayed clear of saying which parts
of the Oracle SOA Suite are used for which areas within our architecture, and there is
a good reason for this. Firstly, we wanted to produce a meaningful architecture that
clearly demonstrated the key objectives and considerations of each layer, rather than
just a piece of marketecture.
Secondly, it's not a simple one-to-one mapping, as within most layers, we have
multiple options available when it comes to implementation.
The first step is to map our architecture to the SOA Suite, which is to determine
which layers should be implemented as SOA composites and deployed to the 11
g
Service Infrastructure and which layers should be implemented as proxy services on
the Oracle Service Bus.
Oracle Service Bus has the concepts of proxy service and business service.
Within our terminology, a proxy service maps to a virtual service.
However, an OSB business service maps to what we have termed an
application service.
We realized this could be confusing and did consider changing our
terminology to match. However, we have tried to base our architecture on
accepted industry practice and terminology. So, we believed it was better
to keep this terminology rather than modify it to it with the naming of
specific products.
There are, as always, a number of ways to do this. However, we will start with
a
simplistic
view of what are regarded as best practices, and then layer on some
additional considerations. The following diagram depicts one way of partitioning
our services across these two components:
