Learn About Network Topologies for Oracle AI Database@Azure
Learn about the various network topology options to select the one best suited for your organizational needs.
The topologies include the following components:
- OCI region
An OCI region is a localized geographic area that contains one or more data centers, hosting availability domains. Regions are independent of other regions, and vast distances can separate them (across countries or even continents).
- OCI virtual cloud
network and subnet
A virtual cloud network (VCN) is a customizable, software-defined network that you set up in an OCI region. Like traditional data center networks, VCNs give you control over your network environment. A VCN can have multiple non-overlapping classless inter-domain routing (CIDR) blocks that you can change after you create the VCN. You can segment a VCN into subnets, which can be scoped to a region or to an availability domain. Each subnet consists of a contiguous range of addresses that don't overlap with the other subnets in the VCN. You can change the size of a subnet after creation. A subnet can be public or private.
- Security list
For each subnet, you can create security rules that specify the source, destination, and type of traffic that is allowed in and out of the subnet.
- Azure Virtual Network and subnet
Azure Virtual Network (VNet) enables you to deploy Azure resources into a private, logically isolated network that you define. This network resembles a traditional on‑premises network, while benefiting from Azure's scalable, highly available cloud infrastructure. After you create a VNet, you can segment it into one or more subnets to organize and control network traffic for your workloads.
- Azure delegated subnet
A delegated subnet is a VNet subnet reserved and delegated to the Oracle AI Database@Azure service, allowing Oracle to deploy and manage the required database resources within your private network IP space.
- VNIC
The servers in OCI data centers have physical network interface cards (NICs). When you create an instance on one of these servers, the instance communicates using Networking service virtual NICs (VNICs) associated with the physical NICs. A virtual network interface card (VNIC) enables an instance to connect to a VCN and determines how the instance connects with endpoints inside and outside the VCN. Each VNIC resides in a subnet in a VCN.
- Azure Virtual WAN
Azure Virtual WAN (VWAN) is a networking service that brings many networking, security, and routing functionalities together to provide a single operational interface.
- Azure route table
Virtual route tables contain rules to route traffic from subnets to destinations outside a VNet, typically through gateways. Route tables are associated with subnets in a VNet.
About Local VNet Topology
The following architecture shows a local VNet topology:
About VNet Peering Topology
If your application components are in different subscriptions from your database components, identify the physical availability zone and colocate the services in the same availability zone to improve latency performance. Finally, allow connection from a peered VNet update OCI NSG of the database.
The following architecture shows a local VNet peering topology:
azure-local-vnet-peering-topology-oracle.zip
For more information on pricing related to VNet peering and Virtual Networks, see the Azure Virtual Network Pricing documentation linked in the Explore More section.
About Hub-and-Spoke VNet Peering Topology
The following architecture shows a hub-and-spoke VNet peering topology with Azure Firewall or NVA:
azure-hub-and-spoke-vnet-peering-topology-oracle.zip
See the Azure Virtual Network Pricing documentation linked in the Explore More section.
About Global Connectivity Between Regions
The following architecture shows global connectivity between regions:
About Connectivity from On-Premises Network with Hub-and-Spoke
The following architecture shows a hub-and-spoke on-premises topology:
