How “OCI Pods” Bring Sub-Millisecond Latency to Azure
If you’re running mission-critical apps in the cloud, you know that speed is everything. Traditionally, “multicloud” meant connecting two different clouds over a distance, which always added a delay. Oracle Database@Azure fixes this by physically changing the map.
Here is how the unique OCI Pod architecture makes sub-millisecond latency possible.
1. Bringing the Cloud to the “Room Next Door”
The biggest reason for the speed is physical proximity. Oracle and Microsoft have partnered to build “Child Sites” directly inside Azure data centers. We call these sites OCI Pods.
Think of an OCI Pod as a physical extension of the Oracle Cloud Infrastructure (OCI). It isn’t a “light” version of the cloud; it contains the exact same hardware and software found in any other OCI region, including:
- Gen2 Network Stack for ultra-fast data movement.
- RDMA Networking to power the massive performance of Exadata and Autonomous Database.
- Off-box Virtualization to ensure your database doesn’t compete for resources.
2. Direct Local Links: No Detours Allowed
In a typical setup, data travels through multiple gateways to get from one provider to another. Oracle Database@Azure uses a direct private network link between the OCI Pod and the Azure network in the same building.
When your Azure app talks to the database, the packets don’t leave the building. They travel through a local link to an edge gateway in the OCI Pod, which hands them directly to your Exadata instance. This “short-circuit” ensures your traffic never leaves the Azure data center, keeping it secure and lightning-fast.
3. Behind the Scenes: Virtual Mapping
When you provision an Oracle Database in your Azure VNet, a bit of “cloud magic” happens under the hood:
- Azure Side: A private IP address is created in your designated Azure subnet.
- OCI Side: Corresponding Virtual Network Interface Cards (VNICs) are created in a private OCI network.
- The Link: A virtual mapping is created between the two. Your Azure app thinks it’s talking to a local resource because, for all intents and purposes, it is.
4. Managed by Oracle, Controlled by You
Even though the hardware lives in an Azure data center, the OCI Control Plane still manages the show. When you click “Create” in the Azure portal:
- Azure sends the request to the Oracle Database@Azure resource provider (hosted in an OCI region).
- OCI validates your identity (often using Identity Federation, so you can just use your Azure login).
- The OCI Control Plane reaches into the pod inside the Azure data center to build your database.
The Result: High Performance, Zero Friction
By using the OCI Pod architecture, you get the best of both worlds. You can use Azure’s AI and app services alongside the world’s fastest database, all while enjoying the same security patching, updates, and operational controls used across all of OCI.
It’s not just two clouds working together—it’s two clouds living together.
