For industrial organizations, the location of a database can be as important as its performance. Data sovereignty rules, security policies, latency requirements, and dependencies on on-premises systems can all make public-cloud migration impractical. Exadata Cloud at Customer offers a different approach: Oracle Exadata Database Service runs in the customer’s data center, with cloud-style provisioning and infrastructure management from Oracle. The X8M generation adds persistent memory, a faster internal network, and updated virtualization to this deployment model.
What Exadata Cloud@Customer changes
The service combines Oracle Database and Exadata infrastructure with a subscription-based cloud operating model, while keeping the system physically on the customer’s premises. Oracle Cloud Operations manages the underlying infrastructure; customers retain responsibility for their database virtual machines, operating system administration, and databases. This division can reduce infrastructure maintenance work without removing customer control over database and application environments.
Because the service uses the same Oracle database technology as on-premises deployments and Oracle Cloud Infrastructure, it is designed to support database migration without application changes. Standard Oracle Net Services clients, including JDBC and OCI, connect applications to the databases. That compatibility can help organizations adopt a hybrid cloud strategy while retaining existing application behavior and database skills.
Exadata Cloud@Customer X8M performance and architecture
X8M combines scale-out database and storage servers with a 100 Gbps Remote Direct Memory Access over Converged Ethernet (RoCE) fabric. The data sheet describes this fabric as providing 2.5 times the bandwidth of the previous generation. Its low-latency connection links compute and storage servers across the system.
Persistent memory (PMEM) adds a storage tier between memory and conventional storage. X8M pairs it with Remote Direct Memory Access (RDMA) algorithms that bypass parts of the network and I/O stack. Oracle’s stated comparison is a reduction in latency from 200 microseconds to less than 19 microseconds for the relevant operations. The platform also uses Kernel-based Virtual Machine (KVM) virtualization and, for quarter-rack and larger configurations, supports up to 1,390 GB of memory per physical server, according to the source data sheet.
Database-aware storage processing
Exadata is built to handle database workloads rather than operate as a generic storage array. For example, Smart Scan moves eligible, data-intensive SQL processing to storage servers. Filtering can happen as data is read, so only rows and columns relevant to a query need to travel to database servers. This parallel processing can reduce unnecessary data movement and database-server CPU work, particularly for analytics.
Other platform capabilities address different workload demands. Storage Indexes can avoid some unnecessary I/O, while Exafusion Direct-to-Wire Protocol supports Oracle RAC messaging over the RoCE network. Hybrid Columnar Compression combines row and columnar techniques to reduce storage needs and I/O, especially for analytic workloads. PMEM and flash features support low-latency data access and writes. These capabilities sit alongside Oracle Database features for transaction processing, analytics, and mixed workloads.
Scaling resources and choosing a configuration
Exadata Cloud@Customer is offered in Base System, quarter-rack, half-rack, and full-rack configurations. Compute capacity can be adjusted online by enabling or disabling OCPUs within the chosen hardware configuration. Storage can also be expanded independently of database-server capacity: the platform supports expansion to as many as 12 storage servers for eligible configurations.
This flexibility may be useful when demand changes by time of day, season, or business cycle. A standby database, for instance, can operate with the resources needed to apply logs and be scaled up if it must take over. The service also supports automation through OCI command-line tools and REST APIs, allowing teams to schedule or script capacity changes. Subscription costs are based on the hardware configuration and enabled compute cores; the source describes customers paying for the compute they use.
Organizations can choose an Enterprise Edition Extreme Performance subscription, which includes Oracle Database options and management packs, or a Bring Your Own License (BYOL) model using eligible existing Oracle Enterprise Edition and option licenses. The data sheet states that Oracle Standard Edition is not supported. Licensing choices should therefore be assessed alongside workload requirements and existing entitlements.
Management, security, and shared responsibilities
The Cloud Control Plane provides web, CLI, and REST API access for lifecycle tasks such as database provisioning, backup, restore, patching, and OCPU scaling. Oracle operates and maintains physical servers, storage, network components, hypervisors, firmware, and Exadata System Software. Customers manage their virtual machines and database environments, with root access to the database VMs and DBA privileges on their databases.
Security controls span infrastructure, networks, virtual machines, and database features. Separate networks support internal RoCE traffic, client connectivity, and backup traffic. Customer-managed virtual machines can be configured with additional security tools and policies. Oracle Operator Access Control provides interfaces to restrict and observe Oracle staff access to infrastructure, including the ability for customers to terminate operator connections. Oracle Cloud Operations does not access customer data to perform infrastructure support, according to the source.
Backup options include the Exadata system’s Fast Recovery Area, Oracle Cloud Object Storage, a local Zero Data Loss Recovery Appliance or NFS filer, and third-party tools installed in customer-managed VMs. The available choices allow backup design to reflect operational and data-protection requirements.
Practical implications for industrial IT teams
Exadata Cloud@Customer X8M is relevant where organizations want database cloud automation but need the database platform in their own data center. It brings together local data residency, Oracle-managed infrastructure, customer-managed database environments, and online resource scaling. Those benefits do not remove the need to plan capacity, licensing, network connectivity, backups, access controls, and ownership of operating tasks.
For plant and enterprise IT leaders, the central decision is whether this balance of on-premises placement and cloud-style operations fits the organization’s constraints. A careful assessment of workload patterns, compliance obligations, existing Oracle investments, and team responsibilities can clarify whether the service supports modernization without requiring a move to public cloud or changes to existing applications.