OCI Foundations - OCI Introduction: Difference between revisions

From Smithnet
Jump to navigation Jump to search
(Created page with "== 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" ** E...")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== OCI Architecture ==
== OCI Architecture ==


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


Design exammple:
Design exammple:
Line 21: Line 21:
== OCI Ditributed Cloud ==
== OCI Ditributed Cloud ==


Hybrid CLoud Services
Hybrid Cloud Services
* Dedicated Regions: at a customer site
* Dedicated Regions: at a customer site
* Oracle Cloud VMware Solution (on OCI public or dedicated)
* Oracle Cloud VMware Solution (on OCI public or dedicated)
Line 28: Line 28:


Dedicated Regions
Dedicated Regions
* Airgapped, will be install, maintain and operated by Oracle
* Airgapped, will be installed, maintained and operated by Oracle
* Customer datacentre of choice
* Customer datacentre of choice
* Use cases:
* Use cases:

Latest revision as of 15:39, 22 September 2023

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 installed, maintained 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