Databases Reference
In-Depth Information
oBay Introduction
By now, you should have a good initial understanding of all the key components that
make up the Oracle SOA Suite. Typically we find that once someone has an initial
grasp of the various components, one of the next questions we get is:
"What is the best way to combine/use all of these different components to
implement a real world SOA solution?"
Answering this question is very much the focus of this section. To do this, we have
built a complete, albeit, relatively small SOA solution designed for an online auction
site for a fictional company called
oBay
(the o stands for Oracle).
Each chapter in this section tackles specific areas that need to be considered when
developing an SOA-based solution, such as the design of the service contract,
validation, error handling, message interaction patterns, and so on. To highlight and
demonstrate key design considerations, each chapter uses examples based on key
parts of the oBay application to illustrate what it is talking about.
This chapter introduces oBay and details the overall business requirements of the
online auction site. Before looking at the overall design of the oBay application, we
take a step back and consider some of the key goals of a SOA-based approach, such
as interoperability, reusability, and agility, and what we mean by that.
Next, we present you with our outline of a typical SOA Architecture, and in
particular, pay attention to how we might want to layer our services, as well as
highlight some of the key design considerations behind this. Only when we have
our blueprint for SOA do we apply it to the business requirements of oBay and
present you with its overall architecture.
