Database Reference
In-Depth Information
Handling
, to the figure under the
Error-handling design rules
section; we would like to
see the relocation of a task-orchestrated service in the context of all SOA runtime frame-
works, and that's not a small thing. Even replication of a VM with a complete OFM in-
stalled is a bit bigger than just copy and paste.
Tip
Here, we are discussing cloud patterns in direct relation to the Oracle SOA technology
stack. Supporting very important patterns such as Elastic Network Capacity, Elastic Disc
Provisioning, Bare-Metal Provisioning, and so on, are out of the scope of this chapter, as
they are lying either on Resource Abstraction and Control Layers or the Physical Re-
source Layer. Cloud ecosystems are based on atomic and compound patterns and mechan-
isms, which are a bit broader than patterns and act as a technology-centric foundation for
the patterns' applications.
How can these cloud undertakings be satisfied? From the bottom to the top, number five
is quite difficult to implement even within the same vendor's environment, but virtually
impossible between different cloud providers. Yes, vendor lock-in in the case of cloud is
one of the biggest risks and the more stateful services we have across our SOA Frame-
works, the more difficult it would be to establish Non-Disruptive Resource Relocation.
This promise will be fulfilled when we will be able to move our most complex task-or-
chestrated services running in production from one cloud provider to another in a matter
of hours, not months. Alas, at the moment of writing this topic, we are far from it.
Number four, Rapid Resource Provisioning, is generally tamed by Oracle for DB, Coher-
ence, and EDN environments across all the required frameworks by creating complete
HW and SW ecosystems as preintegrated Exadata, Exalogic, and Exalytics with lots of
Cloud/SOA supporting appliances (
http://www.oracle.com/us/products/engineered-sys-
tems/index.html
)
. At last, Sun Microsystems together with Oracle made John Gage's pre-
diction true; it was quoted in 1984 that "the network is the computer". In our opinion, it
was a truly brilliant decision to combine such an inventive force into one power, but some
can say that it was an act of desperation as well. Considering the number of products in
Service Inventory
) and the complexity of multilayering a configuration (partly discussed
figured that is tuned for best-performance platforms for enterprises with a shortage of
skillful IT personnel.
Search WWH ::
Custom Search