OCI Foundations: Tenancy, Regions, Availability Domains, and Compartments
Start with Oracle Cloud Infrastructure basics, the OCI control model, tenancy structure, regions, availability domains, and why compartments matter in real deployments.
Inside this chapter
- What Oracle Cloud Infrastructure Is
- Core Cloud Service Models in OCI
- Tenancy, Compartments, and OCIDs
- Regions, Availability Domains, and Fault Domains
- Why Compartments Matter in Real Life
- Shared Responsibility in OCI
- Pricing and Cost Awareness
- A Beginner OCI Picture
Series navigation
Study the chapters in order for the clearest learning path. Use the navigation at the bottom of each page to move from beginner OCI concepts into deeper architecture, governance, and operations topics.
What Oracle Cloud Infrastructure Is
Oracle Cloud Infrastructure, or OCI, is Oracle's public cloud platform for compute, networking, storage, databases, analytics, security, integration, AI, and enterprise infrastructure. Students should not think of OCI only as "Oracle database hosting." It is a full cloud platform used for traditional enterprise applications, cloud-native workloads, data platforms, integration systems, and regulated industry environments.
OCI is especially important in organizations that run Oracle technologies heavily, need strong isolation and enterprise controls, or want cloud infrastructure aligned with databases, middleware, ERP ecosystems, or regulated workloads. But the architectural lessons in OCI also help learners understand general cloud thinking at a deeper level.
Core Cloud Service Models in OCI
| Model | Meaning | OCI Examples |
|---|---|---|
| IaaS | You manage operating systems and more of the runtime stack | Compute, Block Volumes, Virtual Cloud Networks |
| PaaS | You focus more on the application or data service while OCI manages more infrastructure detail | Autonomous Database, OKE, API Gateway |
| Serverless | You mainly manage code, events, and permissions while the platform handles more execution infrastructure | Functions, Events, some managed integration flows |
Students should understand that the service model is a design decision. More control may bring more maintenance. More abstraction may bring faster delivery but fewer low-level tuning options.
Tenancy, Compartments, and OCIDs
OCI has a few identity and governance concepts that every beginner must understand early.
| Concept | Purpose |
|---|---|
| Tenancy | The top-level cloud account and administrative boundary |
| Compartment | A logical container used to organize and isolate resources |
| OCID | A unique Oracle Cloud Identifier for a resource |
Compartments are especially important because OCI policies are often written against compartments. Good compartment design makes governance, billing analysis, and team ownership much easier over time.
Regions, Availability Domains, and Fault Domains
OCI global infrastructure is organized by region, availability domain, and fault domain concepts. These shape placement and resilience decisions.
This matters because resilient architecture is not just about launching instances. It is about how workloads are distributed across failure boundaries.
Why Compartments Matter in Real Life
A company may separate production, non-production, shared services, security, analytics, and platform workloads into different compartments. This improves policy clarity, reduces accidental exposure, and makes it easier to reason about who owns what. Without compartment discipline, OCI estates can become confusing very quickly.
Shared Responsibility in OCI
OCI secures the foundational cloud platform, but customers still control many important responsibilities such as identity policy, resource configuration, application security, secret management, network design, and data handling. Students should understand that managed service does not mean "nothing is our responsibility anymore."
Pricing and Cost Awareness
- Some OCI services charge by provisioned size, runtime, storage, network transfer, or requests
- Architectural decisions affect cost directly
- Idle compute, overprovisioned databases, and weak storage lifecycle choices can create waste
- Tagging, ownership, and cost review improve cloud discipline
Students should begin with the understanding that cloud architecture is always a balance among performance, resilience, security, and cost.
A Beginner OCI Picture
A basic enterprise workload in OCI may use a tenancy, several compartments, IAM policies, a Virtual Cloud Network, compute instances or managed services, block or object storage, and centralized logging or audit visibility. Thinking this way helps students see OCI as a structured cloud environment rather than a loose set of service pages.