OCI Foundations - OCI Introduction

OCI Architecture

• Regions: Localised Geographic regions comprisiong one or more Availability Domains. Choose based on:
  • Close to users for highest performance
  • Data compliance
  • Service availability
• Availability Domains: one or more fault tolernt datacentres located withing a region
  • They are very unlikey to fail simultaneously
  • Connected to each with high bandwith connections
• Fault Domains: Located within an AD, providing a "Logical Datacentre"
  • Each AD has 3 FD
  • Resources in different FD will not share a single point of hardware failure
  • Changes can be specified by FD
  • User specifies which FD to use

Design exammple:

• Replicate App tier over 3 FDs in an AD.
• Do the same for the Database tier
• Then duplicate over another ADs (database can be synchronised using Oracle Dataguard)

OCI Ditributed Cloud

Hybrid CLoud Services

• Dedicated Regions: at a customer site
• Oracle Cloud VMware Solution (on OCI public or dedicated)
• Autonomus DB on Exadata Cloud at Customer site
• Roving Edge Infrastructire (OCI compute and storage for remove disconnected scenarios)

Dedicated Regions

• Airgapped, will be install, maintain and operated by Oracle
• Customer datacentre of choice
• Use cases:
  • Data residency
  • Latency sensite applications

OCI-Azure Interconnect

• Private interconnect (very low latency < 2ms, 12 interconnects)
• Pricing is based on ports/circuits, no charge for bandwitch copnsumed
• Use case: Run application on Azure, DB on OCI
• Oracle Database Service for Azure
  • For Azure customers, they can connect their Azure environments to OCI deployments
  • More automated
  • Unified monitoring in Azure of OCI data