OCI Foundations - Database: Difference between revisions
Jump to navigation
Jump to search
NickPGSmith (talk | contribs) (→MySQL) |
NickPGSmith (talk | contribs) (→NoSQL) |
||
Line 40: | Line 40: | ||
* Excludive to OCI | * Excludive to OCI | ||
== NoSQL == | == NoSQL Database == | ||
* Fully Managed | |||
* Elastic | |||
* High Performance | |||
* Data model flexibility | |||
* Access Control | |||
* Low cost | |||
* Developer freindly APIs | |||
* Always available | |||
* Hybrid cloud/on-premise | |||
Uses cases: many where high volumes of data are involved |
Revision as of 12:28, 22 July 2023
Introduction
Base Database Service:
- Create on VM with block storage
- Provisioning service
Exadata Database Service on dedicated infrastructure
- For Oracle databases
- Comanaged: customer manages DB, Oracle manages infrastructure
Autonomous Database on Shared and dedicated Exadata Infrastrure:
- Self manaaging and repairing
- Shared or dedicated infrastructure
Cloud@Customer:
- At customer datacentre
- Exadata Database Service or Autonomous Database on Exadata
Autonomus DB
Uses machine learning to implement tuning, backups, patching/upgrades
Shared or Dedicated use of Exadata hardware.
- Autonomous Transaction Processing
- Autonomous Data Warehouse
Autonomous JSON Database:
- Designed for noSQL applications
- APEX Service
MySQL Database Service
Host MySQL in the Cloud:
- Standalone, or
- High Availablty: 3 nodes providing auto failover to a secondary instance
MySQL with HeatWave
- Order of magnitude performance improvements
- Enables OLTP and OLAP from the same database
- Excludive to OCI
NoSQL Database
- Fully Managed
- Elastic
- High Performance
- Data model flexibility
- Access Control
- Low cost
- Developer freindly APIs
- Always available
- Hybrid cloud/on-premise
Uses cases: many where high volumes of data are involved