分类
外汇交易技巧和技巧

客户选择 OCI 的原因

NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->

Simple Sidebar

The starting state of the menu will appear collapsed on smaller screens, and will appear non-collapsed on larger screens. When toggled using the button below, the menu will change.

Make sure to keep all page content within the 客户选择 OCI 的原因 #page-content-wrapper . The top navbar is optional, and just for demonstration. Just create an element with the #sidebarToggle ID which will toggle the menu when clicked.

客户选择 OCI 的原因

ORAS

Introduction

Registries are evolving as generic artifact 客户选择 OCI 的原因 客户选择 OCI 的原因 stores. To enable this goal, the ORAS project provides a way 客户选择 OCI 的原因 to push and pull OCI Artifacts to and from OCI Registries.客户选择 OCI 的原因

Users seeking a generic registry client can benefit from the ORAS 客户选择 OCI 的原因 CLI, while developers can build their own clients on top of one of the ORAS client libraries.

What are OCI Registries?

The Open Container Initiative (OCI) defines the specifications and standards for container technologies. This includes the API for working with container registries, known formally as the OCI Distribution Specification. (a.k.a. the "distribution-spec").

The distribution-spec was written based on an open-source registry server originally released by the company Docker, which lives on GitHub at distribution/distribution (now a CNCF project).

There are now a number of other open-source and commercial distribution-spec implementations, a list of which can be found here. Registries that implement the distribution-spec are referred to herein as OCI Registries.

What are OCI Artifacts?

For a long time (pretty 客户选择 OCI 的原因 much since the beginning), people have been using/abusing OCI Registries to store non-container things. For example, you could upload a video to Docker Hub by just stuffing the video file into a layer in a Docker image (don't do this).

The OCI Artifacts project is an attempt to define an opinionated way to leverage OCI Registries for arbitrary artifacts without masquerading them as container images.

Specifically, OCI Image Manifests have a required field known as config.mediaType . According to the guidelines provided by OCI Artifacts, this field provides the ability to differentiate between various types of artifacts.

Artifacts stored 客户选择 OCI 的原因 in an OCI Registry using this method are referred to herein as OCI Artifacts.

How ORAS works

ORAS works similarly to tools you may already be familiar with, such as docker . It allows you to push (upload) and pull (download) things to and from an 客户选择 OCI 的原因 OCI Registry, and also handles login (authentication) and token flow (authorization). What ORAS does differently is shift the focus from container images to other types of artifacts.

ORAS is the de facto tool for working with OCI Artifacts. It treats media types as a critical piece of the puzzle. Container images are never assumed to be the artifact in question.

By default, when pushing artifacts using ORAS, the config.mediaType field is set to unknown:

Authors of new OCI Artifacts are thus encouraged to define their own media types specific to their artifact, which their custom client(s) know how to operate on.

If you wish to start publishing OCI Artifacts 客户选择 OCI 的原因 right away, take a look at the ORAS CLI. Developers who wish to provide their own user experience should use one of the ORAS client libraries.

Connectivity to Oracle Cloud Infrastructure

This section provides 客户选择 OCI 的原因 different connectivity approaches to integrate an Azure landing zone architecture to Oracle 客户选择 OCI 的原因 Cloud Infrastructure (OCI).

Design considerations:

Using ExpressRoute and FastConnect, customers can connect a virtual network in Azure with a virtual cloud network 客户选择 OCI 的原因 in OCI, if the private IP address space doesn't overlap. Once you establish connectivity, resources in the Azure virtual network can 客户选择 OCI 的原因 communicate with resources in the OCI virtual cloud network as if 客户选择 OCI 的原因 客户选择 OCI 的原因 they were both in the same network.

Azure ExpressRoute FastPath is designed to improve the data path performance between two networks, both 客户选择 OCI 的原因 客户选择 OCI 的原因 on-premises and Azure, and for this scenario, between OCI and Azure. When enabled, FastPath sends network traffic directly to virtual machines in 客户选择 OCI 的原因 客户选择 OCI 的原因 the virtual network, bypassing the ExpressRoute gateway.

FastPath is available on all ExpressRoute circuits.

FastPath still requires a virtual network gateway to be created for route exchange purposes. The virtual network gateway must use either the Ultra Performance SKU or the ErGw3AZ SKU for the ExpressRoute gateway to enable route management.

There are features that are currently not supported in ExpressRoute FastPath, such as Azure Virtual WAN 客户选择 OCI 的原因 hubs or VNet peering.

While you can use ExpressRoute Global Reach to enable communication from on-premises to OCI via ExpressRoute circuits, it might incur more bandwidth costs that you can calculate by using the Azure pricing calculator. It's important to consider any extra 客户选择 OCI 的原因 costs when you migrate large amounts of data from on-premises to Oracle by using ExpressRoute circuits.

In Azure regions that support Availability 客户选择 OCI 的原因 Zones, placing your Azure workloads in one zone or the other can have a small effect on latency. Design your application to 客户选择 OCI 的原因 客户选择 OCI 的原因 balance availability and performances requirements.

Interconnectivity between Azure and OCI is only available for specific regions.

Design recommendations:

Create the ExpressRoute circuit that 客户选择 OCI 的原因 will be used to interconnect Azure with OCI in the connectivity 客户选择 OCI 的原因 subscription.

You can interconnect an Azure network architecture based on the traditional hub and spoke architecture or Azure Virtual WAN-based network topologies. It can be done by connecting the ExpressRoute circuit that will be used to interconnect Azure to OCI to the hub VNet 客户选择 OCI 的原因 or Virtual WAN hub as shown in the following diagram.

Diagram that shows interconnectivity between Azure and O C I via ExpressRoute.

Figure 1: Interconnectivity between Azure and OCI via ExpressRoute.

If your application requires the lowest possible latency between Azure and OCI, consider deploying your application in a single VNet with an ExpressRoute gateway and 客户选择 OCI 的原因 FastPath enabled.

Diagram that shows Azure to O C I - single V Net.

Figure 2: Interconnectivity between Azure and OCI with a single VNet.

When you deploy Azure resources across Availability Zones, perform 客户选择 OCI 的原因 latency tests from Azure VMs located in different Availability Zones to OCI resources to understand which of the three Availability Zones provides the lowest latency to the OCI resources.

To operate Oracle resources hosted 客户选择 OCI 的原因 in OCI by using Azure resources and technologies, you could:

From Azure: Deploy a jump box in a spoke VNet. The jump box provides access to the virtual cloud network in OCI as shown in the following picture:

Diagram that shows Azure to OCI jump box on one VNet.

Figure 3: Managing OCI resources 客户选择 OCI 的原因 from Azure via a jump box.

From on-premises: Use ExpressRoute Global Reach to bind an existing ExpressRoute circuit that connects on-premises 客户选择 OCI 的原因 to Azure, to an OCI ExpressRoute circuit that interconnects Azure to OCI. In this way, the Microsoft Enterprise Edge (MSEE) router becomes the central routing point between both ExpressRoute circuits.

Diagram that shows Azure to OCI via Global Reach.

Figure 4: Managing OCI resources from on-premises via ExpressRoute Global Reach.

Next steps

For information on connectivity to other cloud providers, see Connectivity to other cloud providers.