Oracle MAA
Reference Architectures
Oracle
Database High Availability On-Premises and in the Cloud
Oracle White Paper
Introduction
Enterprises
are under intense pressure to do more with less, reduce risk and increase
agility. The aggressive consolidation of information technology (IT)
infrastructure and deployment of Database as a Service (DBaaS) on public and
private clouds is a strategy that many enterprises are pursuing to accomplish
these objectives.
Database
consolidation drives cost savings by dramatically improving system utilization
and reducing management overhead. DBaaS drives cost savings and increased
agility through the standardization of I.T. infrastructure and processes. The
Cloud enhances these benefits by enabling a more efficient utility model of
computing.
All of the
above initiatives, however, also incur business risk by amplifying the impact
of downtime and data loss. The failure of a standalone environment used by a
single developer or small work group is usually of limited impact. The failure
of a critical application running in a traditional standalone environment will
be immediately felt by the business, but other applications can continue to run
unaffected. In contrast, an outage of a consolidated environment supporting an
organization’s entire development staff or multiple applications used by
numerous departments would have a crippling effect on the business. Equally
crippling would be an interruption in service at a cloud provider where such
applications are running.
The Oracle
Maximum Availability Architecture (Oracle MAA) prescribes four HA reference
architectures that provide the requisite level of standardization for DBaaS
while addressing the complete range of availability and data protection
required by enterprises of all sizes and lines of business. All reference
architectures are based upon a common platform able to be deployed onpremises
or on cloud. This approach makes Oracle MAA simpler and less risky to move to
the cloud.
This paper
describes Oracle MAA reference architectures in detail and the service level
requirements that they address. It is most appropriate for a technical
audience: Architects, Directors of IT and Database Administrators responsible
for designing and implementing DBaaS and moving to the cloud.
No hay comentarios:
Publicar un comentario