Autonomous Database in OCI
By shrikaneAutonomous Database in OCI
Introduction
- OCI helps in moving from a traditional based CAPEX model to OPEX based culture.
- OCI also supports Cloud@Customer which can run behind company’s firewall and solves data sovereignty requirements.
- OCI ADB is self-driving, self-securing and self-repairing fully managed database environment available on cloud as well as on-premises.
- Four distinct types of workloads are available,
- Autonomous Transaction Processing (ATP)
- Autonomous Data Warehouse (ADP)
- Application Express (APEX)
- Autonomous JSON Database (AJD)
- Scale the number of CPU cores or the storage capacity of the database at any time without impacting the availability or performance of the database system.
- ML models and algorithms runs inside Oracle ADB
- All data in ADB is encrypted.
- Security at both rest and in motion. All connections use certificate-based authentication over SSL.
- ADB provides network Access Control List (ACL), to be able to configure allowed IP addresses and reject all other.
- Also provides access through private endpoints thus allowing accessing only from inside a VCN.
- Customers can create ADB using,
- CLI
- OCI Console
- SDK
- Terraform
- ADB is built on OCI Exadata infrastructure.
- Each ADB database is an independent pluggable database (PDB), to which the customer doesn’t have the host access.
- Exadata machine is combination of hardware and software optimized to run oracle database.
- Oracle ADW is designed to run data warehousing, data marts, data lakes, analytics and ML workloads.