← All databases and providersHow to build the shortlist.
- Identify the Oracle version, PL/SQL dependencies, certified application requirements, and licensed options before deciding whether to retain or migrate the engine.
- Compare a self-managed Oracle deployment with the actual Autonomous service restrictions and workload configuration. Automation changes operating responsibilities, not application requirements.
- MySQL HeatWave and Oracle NoSQL are different data-platform choices. Match their query and transaction model to the job instead of assuming all Oracle products share one engine.
Review the exact product, region, version, and service configuration before making a production decision. Sources checked September 8, 2026.
Provider’s database overview ↗5 engines and services to compare.
Oracle · Database engine
MySQL
Relational
Self-managed engine; many providers offer managed hosting
When to consider it
An established relational option for web applications and services with a MySQL-compatible ecosystem. Existing team experience, application support, and operational procedures may make it a practical first candidate.
What to check
Check the storage engine, SQL modes, transaction isolation, indexing, and migration requirements. MySQL, MariaDB, Aurora MySQL, and HeatWave should not be treated as interchangeable products.
Official documentation ↗Oracle · Managed service
MySQL HeatWave
Relational / Analytics
Managed MySQL with optional HeatWave capabilities; cloud offerings vary
When to consider it
Evaluate HeatWave when MySQL transactional data and accelerated analytical queries are useful together. Compare the selected service configuration with ordinary managed MySQL and a separate analytical warehouse.
What to check
A DB system and a HeatWave cluster are distinct parts of the configuration. Check the actual cloud offering, supported features, sizing, data loading, and cost.
Official documentation ↗Oracle · Database engine
Oracle AI Database
Relational
Oracle Database engine; on-premises and cloud deployment options
When to consider it
A central candidate for existing Oracle applications, PL/SQL code, and enterprise systems that depend on Oracle database features. The current product name is Oracle AI Database; compatibility still depends on version and deployment.
What to check
Review edition and option licensing, application certification, operational skills, and migration dependencies. A new engine can require rewriting database-specific code and administration workflows.
Official documentation ↗Oracle · Managed service
Oracle Autonomous AI Database
Relational / Analytics
Oracle managed database service; deployment and workload choices vary
When to consider it
Consider it for Oracle SQL and PL/SQL workloads where managed patching, tuning, and database operations fit the application. Select a transactional or analytical workload configuration deliberately.
What to check
Automation does not establish application compatibility or recovery readiness. Check database restrictions, integration dependencies, licensing model, workload configuration, and export requirements.
Official documentation ↗Oracle · Managed service
Oracle NoSQL Database Cloud Service
Key-value / Document
Oracle Cloud; managed NoSQL tables and key-oriented access
When to consider it
An option for applications that fit key-oriented tables and flexible records in Oracle Cloud. Evaluate table design, throughput needs, and regional access patterns against the service model.
What to check
Do not assume relational joins or Oracle Database transaction semantics. Validate consistency, request limits, capacity choices, and global-table conflict behavior.
Official documentation ↗Continue your work
Take the next step.