Oracle AI Database@Azure: Why It Matters and When to Use It
Oracle Database@Azure was announced by Oracle and Microsoft
in September 2023. The picture shows the regions having oracle database@azure.
We may wonder that we
have option of running Oracle database in Azure VM or we can create interconnect
(Fast connect + Express Route) between OCI and Azure and the applications in
Azure can access the database in OCI, then what is benefit of choosing Oracle database@Azure
model. We are going to discuss in detail in this article.
Oracle AI Database@Azure in simple terms, it is a jointly integrated Oracle and Microsoft offering that allows organizations to deploy Oracle database services inside Microsoft Azure data centers. The underlying database infrastructure remains based on Oracle Cloud Infrastructure technologies, but the infrastructure is physically located in Azure facilities. Applications running on services such as Azure Virtual Machines or Azure Kubernetes Service can therefore access Oracle databases through Azure networking rather than treating the database as a remote workload hosted in another public cloud. Unlike Oracle database in Azure VM where oracle is installed and managed manually in Azure environment, Oracle provides its database cloud services on Oracle infrastructure physically deployed inside Azure data centers and integrated with Azure. Some Important features of this model:
· Oracle database infrastructure is colocated in
Azure data centers.
· Networking uses Azure Virtual Network.
· Azure identity and authorization mechanisms
participate in service access.
· Database metrics, logs, events, and telemetry
can be surfaced within Azure.
· Oracle operates and maintains the underlying
Oracle infrastructure.
· Azure portal, APIs, SDKs, and Terraform can be
used for many provisioning and management activities.
The above features make Oracle AI Database@Azure
fundamentally different from installing Oracle Database software on a standard
Azure VM.
In the Interconnect model, the connection between OCI and
Azure is created and managed by users. But in the Oracle database@azure, the
higher bandwidth connectivity is in-built.
|
|
Oracle
Database on Azure VM |
Oracle AI
Database@Azure |
Oracle
Database in OCI + Azure Interconnect |
|
Oracle Database
Location |
Azure VM |
On OCI
database infrastructure colocated inside Azure datacenters |
In an OCI
region |
|
Cloud
model |
Azure IaaS |
Oracle DBaaS
integrated into Azure |
Azure + OCI |
|
Infrastructure
owner |
Microsoft
provides VM infrastructure |
Oracle
operates OCI database infrastructure inside Azure |
Oracle
operates OCI infrastructure in OCI |
|
Patching |
Customer
handles OS/DB patching |
Oracle
handles infrastructure patching; DB patching varies by service |
Oracle
handles cloud infrastructure; DB patching varies by OCI service |
|
Network |
Native Azure
networking |
Private
Azure-integrated connectivity |
Azure
ExpressRoute + OCI FastConnect |
|
Latency
between Azure app and DB |
Azure-local |
Very low
latency; DB infrastructure colocated in Azure |
Low latency,
but traffic crosses Azur and OCI private interconnect |
|
Cross-cloud
network required |
No |
No
traditional Azure-to-OCI interconnect needed for DB access |
Yes |
|
Exadata &
Autonomous database |
No |
Yes |
Yes, if using
Exadata & Autonomous database in OCI |
|
RAC availability |
No |
Available |
Available
with supported OCI database services. |
|
Performance
model |
Depends on
Azure VM + storage sizing |
Oracle
engineered infrastructure, especially Exadata |
Oracle OCI
database infrastructure |
|
Billing |
Azure
compute/storage/network billing and Oracle database licensing separately |
Purchased
through Azure Marketplace and billing appear in Azure portal. |
OCI DB
billing + Azure services billing separately |
|
Operational
complexity |
customer-managed |
Lowest of the
three for Azure centric Oracle DBaaS |
Higher
because two clouds, routing, identity and operations must be coordinated |
|
Monitoring |
Customer
configures monitoring |
Native Azure
Monitor integration is supported |
Requires
integration, export & configuration across clouds |
|
Best Fit |
Lift-and-shift,
Development and Testing, smaller/custom Oracle environments |
Mission-critical
Oracle workloads closely integrated with Azure |
Existing OCI
estate or workloads that need OCI services while applications stay in Azure |
·
Mission critical Oracle Database: We will get
fully managed Oracle hardware sitting right inside Azure data centers, giving us
top tier speed and reliability without needing a hybrid setup.
·
Very high DB performance: The co-located
hardware delivers low-latency, high-speed performance for demanding, data-heavy
applications.
·
Exadata: Oracle database@azure provides Oracle
Exadata Database Service to handle massive compute and storage demands effortlessly.
·
RAC: It is an Instance HA option. Oracle RAC
distributes workloads across multiple server instances so the app stays online
even if a server fails.
·
Data Guard: Oracle Data Guard keeps standby
databases synced in real time to protect against outages and data loss.
·
Autonomous Database: Oracle Autonomous Database for
handling routine work like provisioning, patching, scaling, and tuning
automatically.
·
Oracle AI Database 26ai: The latest database
version with AI features enabled which let us run vector searches and AI
workloads directly alongside our existing enterprise data.
·
Azure applications + Oracle DB: Azure VMs,
microservices on AKS and custom apps connect directly to Oracle databases over
private, low-latency links.
·
Microsoft Fabric / AI integration: Integrate our
Oracle data straight into Microsoft Fabric and Azure AI services for analytics
and reporting.
·
Enterprise Oracle workload: Easily powers
critical ERP, financial, and transactional systems right inside an Azure-based
setup.
·
Low operational overhead: Oracle takes care of
the underlying hardware and infrastructure management, freeing up our internal
IT team.
No comments:
Post a Comment