ExaCC is Oracle Exadata installed in customer premises but managed as a cloud service through OCI, whereas ExaCS is Exadata infrastructure fully hosted and managed inside Oracle Cloud Infrastructure regions. ExaCC is preferred for data residency and low-latency on-prem requirements, while ExaCS is preferred for full cloud adoption and elastic scalability.
ExaCC (Cloud@Customer)
Oracle installs Exadata rack physically at customer site.
Architecture Flow :-
Customer Data Center –> Exadata Rack –> Managed by OCI Control Plane
Customer get:
- Cloud automation
- OCI APIs
- Autonomous capabilities
- But data never leaves premises
Best when:
- Regulations prevent cloud migration
- Low latency to on-prem apps required
- Strict data governance needed
Example:
A bank wants Exadata cloud benefits but cannot move customer data outside their own DC.
Think Like – OCI Cloud services running INSIDE customer data center
ExaCS (Exadata Cloud Service)
Everything stays in Oracle cloud.
Architecture Flow :
Oracle OCI Region –> Exadata Infrastructure –> Customer databases run in OCI
Best when:
- Organization is cloud-ready
- Wants elastic scaling
- Wants OCI ecosystem integration
- No on-prem dependency
Example:
A SaaS company hosting production Oracle databases fully in OCI.
Think Like – Exadata running directly inside Oracle OCI.
Comparison Table :-
| ExaCC vs ExaCS | ||
|
Feature |
ExaCC | ExaCS |
| Full Form | Exadata Cloud@Customer | Exadata Cloud Service |
| Deployment Location | Customer Data Center (On-Premises) | Oracle Cloud Infrastructure (OCI) |
| Hardware Ownership | Oracle-owned and managed hardware installed at customer site | Oracle-owned hardware inside OCI regions |
| Physical Location | Inside your company DC | Inside Oracle OCI DC |
| Cloud Experience | Yes | Yes |
| Control Plane | Connected to OCI | Native OCI |
| Connectivity Requirement | Requires OCI connectivity | Already inside OCI |
| Data Residency | Data stays inside customer premises | Data stored in OCI |
| Best For | Regulatory / data sovereignty needs | Full cloud adoption |
| Latency to On-P Apps | Very low | Depends on network connectivity |
| Infrastructure Management | Oracle manages hardware/software | Oracle manages hardware/software |
| Scalability | Limited by installed rack capacity | Highly elastic |
| Expansion | Need physical expansion | Easier online scaling |
| Cost Model | Subscription + on-prem install | Pure cloud subscription |
| Internet Dependency | Less external dependency | Cloud dependent |
| Disaster Recovery | Usually customer-managed or OCI hybrid | OCI-native DR options |
| Typical Users | Banks, government, healthcare | Cloud-native enterprises |
Operational Difference:-
|
Task |
ExaCC | ExaCS |
| Rack Installation | Oracle installs at customer site | Already available in OCI |
| Power/Cooling | Customer responsibility | Oracle responsibility |
| Physical Security | Customer DC | Oracle DC |
| Hardware Replacement | Oracle field engineers visit customer site | Oracle internal |
| Capacity Increase | Physical rack expansion | OCI scaling |