Oracle Base Database Service
Oracle Database connections using the database listener and application service name.
Database accelerator for Oracle Cloud
Keep your Oracle Database, MySQL or PostgreSQL service. Add EngineGrids Accelerator to reduce repeated database work and put your cloud capacity to better use.
Managed Oracle Cloud databases
Connect EngineGrids Accelerator to your database’s native SQL endpoint. Keep your database, application drivers and data in place.
Oracle Database connections using the database listener and application service name.
Oracle Database on Dedicated or Exascale Infrastructure, using the service’s Oracle Net and SCAN connection details.
Oracle SQL connections using the selected database service and its TLS or wallet-based mTLS settings.
MySQL application traffic through the DB system’s classic MySQL protocol endpoint.
Managed PostgreSQL connections through the database system’s private endpoint.
How it works
System of record
Deploy Accelerator in your Oracle Cloud network between applications and the database service. Reduce repeated database reads while your database remains the system of record.
Connection planning
Point your application’s existing database connection at Accelerator. Configure its database-facing connection with the original endpoint, database or service name and authentication. Provide private network access through your VCN and allow the required listener traffic. The normal setup requires no application source changes or data migration.
For Base Database and Exadata, retain the application service name and configure the database hostname or SCAN listener. Accelerator follows listener redirects on the database-facing connection while applications stay connected to Accelerator.
For Autonomous Database, use the selected service’s TLS or wallet-based mTLS connection details. Configure trust and any required backend client certificate separately from application-facing TLS. For TCPS redirects, verify every listener against the configured certificate authority and service identity.
For MySQL HeatWave, use the classic MySQL endpoint from the DB system. For OCI Database with PostgreSQL, use the private database endpoint and retain its TLS hostname and certificate verification.
Run Accelerator alongside supported databases you manage on Oracle Cloud compute as well. MySQL, PostgreSQL, SQL Server, Oracle Database and Db2 LUW follow the same native SQL connection model, separate from the managed services above.
Business value
Lower database demand can create room to reduce provisioned compute or support more work at the same capacity. Review eligible database license costs when the required licensed capacity changes.
More headroom without a larger database plan
Evaluate Base Database compute allocation, enabled Exadata compute, or Autonomous Database base capacity and autoscaling demand. Compare the resources you can actually resize while preserving performance and availability.
For MySQL HeatWave and OCI Database with PostgreSQL, evaluate database compute and memory against your workload. Account for HeatWave cluster resources and database storage separately.
Keep Exadata infrastructure or reserved capacity, storage, backups and networking as separate cost lines. Include Accelerator operation and review license-included or eligible bring-your-own-license terms for the proposed configuration.
Compare workload demand, a suitable compute configuration, software licensing and the Accelerator footprint using your own prices.
Performance Lab
Evaluate EngineGrids in your own cloud environment. Compare workload performance and database demand.
Get started
Start with a 30-day free trial, then continue your deployment through the purchasing route that fits your business.