You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
Understanding OCI's infrastructure helps you design applications that are fast, resilient, and compliant. This lesson covers regions, availability domains, fault domains, and Oracle's unique infrastructure offerings.
A region is a geographic area containing one or more availability domains. OCI operates 50+ regions globally.
| Region | Region ID | Location |
|---|---|---|
| US East (Ashburn) | us-ashburn-1 | Virginia, USA |
| US West (Phoenix) | us-phoenix-1 | Arizona, USA |
| UK South (London) | uk-london-1 | United Kingdom |
| Germany Central (Frankfurt) | eu-frankfurt-1 | Germany |
| Japan East (Tokyo) | ap-tokyo-1 | Japan |
| Australia East (Sydney) | ap-sydney-1 | Australia |
| Brazil East (São Paulo) | sa-saopaulo-1 | Brazil |
| India West (Mumbai) | ap-mumbai-1 | India |
| Canada Southeast (Toronto) | ca-toronto-1 | Canada |
| South Korea Central (Seoul) | ap-seoul-1 | South Korea |
Consider:
An availability domain is one or more data centres within a region, designed for high availability:
Region: us-ashburn-1
├── AD 1 (Availability Domain 1)
├── AD 2 (Availability Domain 2)
└── AD 3 (Availability Domain 3)
↕ Low-latency private links ↕
Most OCI regions have a single availability domain with multiple fault domains. Larger regions (like Ashburn and Phoenix) have three availability domains.
Fault domains provide anti-affinity within an availability domain:
Availability Domain 1
├── Fault Domain 1 (Hardware Group A)
├── Fault Domain 2 (Hardware Group B)
└── Fault Domain 3 (Hardware Group C)
Use case: Place your application servers across fault domains so that hardware failure or maintenance on one group does not affect all instances.
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.