dmassaro82/oci-deal-accelerator
1
0
Fork 0
forked from diegoecab/oci-deal-accelerator
Code Pull Requests Activity

initial version

Browse Source
This commit is contained in:
Diego Cabrera
2026-03-18 18:03:44 -03:00
commit 9d269e902b
136 changed files with 28175 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

80
kb/services/adb-dedicated.yaml Normal file
View File

@@ -0,0 +1,80 @@
---
last_verified: 2026-03-14
service: Autonomous Database Dedicated (ADB-D)
category: database
oci_color: "#AA643B"
---
what: Autonomous Database on dedicated Exadata infrastructure. Provides isolation,
higher resource limits, and more control while retaining autonomous operations
(auto-patching, auto-tuning, auto-scaling).
when_to_use:
- Regulatory/compliance requirement for dedicated infrastructure
- Need for container database (CDB) level control
- Sustained workloads >128 OCPUs per database
- Multiple databases that benefit from shared Exadata infrastructure
- Organizations that want autonomous features but need infrastructure isolation
- Need to control maintenance windows precisely
when_NOT_to_use:
- Small/medium workloads (ADB-S is simpler and cheaper)
- Teams that don't need infrastructure isolation
- Budget-constrained projects (dedicated infrastructure has higher base cost)
- Rapid prototyping or dev/test (ADB-S provisions faster)
limits:
max_ocpu_per_vm_cluster: 400
max_adb_per_vm_cluster: 200
max_storage_per_vm_cluster_tb: 192
min_exadata_infrastructure: "Quarter rack (base)"
max_vm_clusters_per_infra: 8
features:
auto_scaling: true
auto_indexing: true
auto_partitioning: true
autonomous_data_guard: true
cross_region_adg: true
private_endpoint: true
customer_managed_keys: true
fleet_management: true
maintenance_window_control: true
resource_pool_management: true
os_access: false
rac: false # Not traditional RAC, but Exadata-managed HA
ha_dr:
local_ha: "Exadata-managed, automatic failover within infrastructure"
autonomous_data_guard:
same_region: "Synchronous, automatic failover"
cross_region: "Asynchronous, manual or automatic failover"
sizing_rules:
minimum_infrastructure: "Quarter rack equivalent"
ocpu_allocation: "Shared across all ADBs in the VM cluster"
storage_allocation: "Shared Exadata storage pool"
pricing:
model: dedicated_infrastructure
infrastructure_base: "Exadata infrastructure (fixed cost per shape)"
ocpu_payg: "Per OCPU per hour on top of infrastructure"
byol_discount: "~50% on OCPU costs"
notes:
- "Infrastructure cost is fixed regardless of utilization"
- "OCPU billing is for databases provisioned on the infrastructure"
- "Higher base cost but better economics at scale (>128 OCPUs sustained)"
gotchas:
- id: ADB-D-001
issue: "Provisioning infrastructure takes hours, not minutes"
impact: "Cannot spin up quickly like ADB-S"
recommendation: "Plan infrastructure provisioning well ahead of database needs"
- id: ADB-D-002
issue: "Minimum infrastructure commitment"
impact: "Even at low utilization, you pay for the base infrastructure"
recommendation: "Only choose ADB-D when sustained usage justifies the base cost"
- id: ADB-D-003
issue: "Maintenance windows affect all databases on the infrastructure"
impact: "Need to coordinate maintenance across all tenants"
recommendation: "Use maintenance window control to schedule during off-peak"

49
kb/services/adb-elastic-pool.yaml Normal file
View File

@@ -0,0 +1,49 @@
---
last_verified: 2026-03-14
service: Autonomous Database Serverless Elastic Pool
category: database
oci_color: "#AA643B"
---
what: Pool of pre-provisioned ADB-S resources that multiple databases share.
Reduces provisioning time and allows resource sharing across databases.
when_to_use:
- Many small databases (SaaS per-tenant model)
- Need fast provisioning (<1 minute vs 2-5 minutes for standard ADB-S)
- Workloads with staggered peak times across databases
- Dev/test environments with many short-lived databases
when_NOT_to_use:
- Single large database (just use ADB-S directly)
- All databases peak simultaneously (no benefit from pooling)
- Need strict resource isolation between databases
limits:
max_ocpu_per_pool: 512
max_databases_per_pool: 1000
max_storage_per_pool_tb: 4096
features:
shared_resources: true
fast_provisioning: true
auto_scaling: "Per database within pool limits"
leader_follower: "Leader database manages pool, followers consume"
pricing:
model: pool_based
pool_ocpu_payg: "Per OCPU per hour for the pool"
notes:
- "Pool resources are billed whether databases use them or not"
- "Individual databases draw from the pool allocation"
- "Cost-effective when average utilization across pool is >50%"
gotchas:
- id: EP-001
issue: "Pool resources are committed even when idle"
impact: "Under-utilized pools cost more than individual ADB-S instances"
recommendation: "Size pool for aggregate average, not sum of peaks"
- id: EP-002
issue: "Noisy neighbor risk within pool"
impact: "One database can consume disproportionate resources"
recommendation: "Set per-database OCPU limits to prevent resource hogging"

146
kb/services/adb-serverless.yaml Normal file
View File

@@ -0,0 +1,146 @@
# OCI Service: Autonomous Database Serverless (ADB-S)
# Last verified: 2026-03
service:
name: "Autonomous Database Serverless (ADB-S)"
id: adb_serverless
category: database
color: "#AA643B"
features:
auto_scaling: true
auto_indexing: true
auto_tuning: true
auto_patching: true
transparent_application_continuity: true
autonomous_data_guard: true
private_endpoints: true
byol_eligible: true
ha_dr_options:
local_ha: "Built-in TAC (Transparent Application Continuity) — ~0 perceived RTO"
same_region_adg: "Autonomous Data Guard standby — synchronous, RPO 0"
cross_region_adg: "Cross-region ADG — asynchronous only, RPO seconds, RTO < 15 min"
limits:
max_ocpu: 128
max_storage_tb: 383
max_auto_scale: "3x base OCPUs"
auto_scale_activation: "2-3 minutes"
min_ocpu: 1
min_storage_tb: 1
variants:
- id: adb_s
name: "Autonomous Database Serverless (ADB-S)"
description: "Shared Exadata infrastructure, fully managed, auto-scaling"
workload_types:
- ATP (Transaction Processing / Mixed)
- ADW (Data Warehouse / Analytics)
- AJD (JSON Document Store)
- APEX (Low-code application development)
- id: adb_d
name: "Autonomous Database on Dedicated Exadata (ADB-D)"
description: "Dedicated Exadata infrastructure, full isolation"
use_when:
- "Strict isolation requirements (regulatory, multi-tenant)"
- "Predictable performance with no noisy-neighbor risk"
- "Need RAC for horizontal compute scaling"
- "> 128 OCPUs sustained"
when_to_use:
- "Oracle Database workloads migrating to cloud"
- "Need automated patching, tuning, and scaling"
- "BYOL opportunity with existing Oracle DB licenses"
- "JSON document workloads (AJD)"
- "Rapid APEX application development"
- "Data warehouse / analytics with auto-scaling"
when_not_to_use:
- "Non-Oracle database engines (use MySQL HeatWave, PostgreSQL, NoSQL)"
- "Need OS-level access or custom DB home configuration → use DBCS"
- "Need RAC but not ADB-D budget → use ExaCS or DBCS VM"
- "Workloads requiring specific DB patches not yet in ADB"
- "Extreme IOPS requirements > what Exadata provides"
sizing:
adb_s:
min_ocpu: 1
max_ocpu: 128
auto_scaling: "Up to 3x base OCPUs (takes 2-3 minutes to activate)"
sizing_guidance: "Size base OCPUs for P75 sustained load, not P50. Auto-scaling covers peaks but has activation latency."
storage_min_tb: 1
storage_max_tb: 383
iops: "Proportional to OCPU count, Exadata storage servers"
adb_d:
min_ocpu: "2 per VM (minimum 2 VMs for HA)"
max_ocpu: "Per Exadata infrastructure shape"
rac: true
storage: "Exadata storage dependent on infrastructure shape"
gotchas:
- id: adb_s_autoscale_latency
severity: MEDIUM
description: "Auto-scaling activation takes 2-3 minutes. Size base OCPUs for P75, not average."
- id: adb_s_private_endpoint
severity: HIGH
description: "Always use private endpoints for production. Public endpoints allow internet access to the DB listener."
- id: adb_s_service_gateway
severity: MEDIUM
description: "ADB-S requires a Service Gateway in the VCN for automated backups to Object Storage."
- id: adb_s_byol_savings
severity: LOW
description: "BYOL pricing is ~50% cheaper than License Included. Always check if customer has existing Oracle DB licenses."
- id: adb_d_minimum_infra
severity: HIGH
description: "ADB-D requires dedicated Exadata infrastructure — minimum cost is significant. Don't recommend for small workloads."
- id: adb_data_guard_async
severity: MEDIUM
description: "Cross-region Autonomous Data Guard is async only (RPO > 0). For zero RPO, need same-region standby or ADB-D with local Data Guard."
- id: adb_19c_only
severity: LOW
description: "ADB currently runs Oracle 19c. If customer needs 23ai features, verify availability."
implied_dependencies:
- service: service_gateway
reason: "Required for automated backups to Object Storage"
- service: private_endpoint
reason: "Production workloads must use private endpoints"
- service: oci_vault
reason: "Customer-managed encryption keys (recommended for production)"
- service: data_safe
reason: "Security assessment, audit, and data masking"
competitive:
vs_aws_rds:
advantages:
- "Autonomous operations (auto-patching, auto-tuning, auto-scaling)"
- "Dramatically lower DB licensing cost with BYOL"
- "Exadata performance for Oracle workloads"
disadvantages:
- "No multi-engine support (Oracle only)"
- "Auto-scaling latency vs. Aurora's faster scale-out"
vs_azure_sql:
advantages:
- "Oracle-native features (RAC, Data Guard, Advanced Compression)"
- "BYOL cost advantage"
disadvantages:
- "Azure has broader SQL Server ecosystem integration"
references:
documentation: "https://docs.oracle.com/en/cloud/paas/autonomous-database/"
pricing: "https://www.oracle.com/autonomous-database/pricing/"
sizing_guide: "https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-database-cpu.html"
changelog:
- date: "2026-03-14"
contributor: { name: "Diego Cabrera", team: "Field Architecture" }
change: "Initial creation with sizing rules, gotchas, competitive notes, HA/DR options"

73
kb/services/compute.yaml Normal file
View File

@@ -0,0 +1,73 @@
---
last_verified: 2026-03-14
service: OCI Compute
category: compute
oci_color: "#4F7B6E"
---
what: Virtual machines and bare metal instances. Flexible shapes allow custom
OCPU/memory ratios. AMD, Intel, and Arm options available.
shape_families:
- name: VM.Standard.E5.Flex
processor: "AMD EPYC 9J14 (Genoa)"
max_ocpu: 94
memory_per_ocpu_gb: "1-64 GB per OCPU"
use_for: "General purpose, most workloads"
- name: VM.Standard3.Flex
processor: "Intel Xeon (Ice Lake)"
max_ocpu: 32
memory_per_ocpu_gb: "1-64 GB per OCPU"
use_for: "Intel-optimized workloads"
- name: VM.Standard.A2.Flex
processor: "Ampere Altra (Arm)"
max_ocpu: 80
memory_per_ocpu_gb: "1-64 GB per OCPU"
use_for: "Arm-compatible workloads, cost optimization"
- name: VM.Optimized3.Flex
processor: "Intel Xeon (Ice Lake)"
max_ocpu: 18
memory_per_ocpu_gb: "1-64 GB per OCPU"
use_for: "High-frequency trading, HPC"
- name: VM.GPU.A10.1
processor: "NVIDIA A10"
gpu_count: 1
use_for: "AI/ML inference, GPU workloads"
- name: BM.GPU.H100.8
processor: "NVIDIA H100 (8 GPUs)"
gpu_count: 8
use_for: "AI/ML training, large model inference"
when_to_use:
- Traditional VM-based applications
- Applications not suited for containers
- Database clients and application servers
- Bastion hosts and jump boxes
- GPU workloads (AI/ML, rendering)
when_NOT_to_use:
- Containerized microservices (use OKE)
- Serverless event-driven workloads (use Functions)
- Managed database workloads (use ADB/DBCS)
features:
flexible_shapes: true
burstable: "Burstable instances available (VM.Standard.E5.Flex.Burstable)"
preemptible: "Preemptible instances at reduced cost"
dedicated_hosts: true
live_migration: true
boot_volume_backup: true
instance_pools: true
autoscaling: "Instance pool autoscaling"
pricing:
model: per_ocpu_per_hour
e5_flex_per_ocpu: 0.0230
standard3_flex_per_ocpu: 0.0360
a2_flex_per_ocpu: 0.0100
memory_per_gb: 0.0015
preemptible_discount: "~50% off on-demand"
notes:
- "Flexible shapes: OCPU + memory billed separately"
- "Always Free tier: 1 VM.Standard.E2.1.Micro (AMD)"
- "Preemptible instances can be reclaimed with 30s notice"

186
kb/services/database-at-aws.yaml Normal file
View File

@@ -0,0 +1,186 @@
# Oracle Database@AWS — KB Service Card
# Last verified: 2026-03-17
# Sources:
# - https://www.oracle.com/cloud/aws/
# - https://docs.oracle.com/en-us/iaas/Content/database-at-aws/oaaws.htm
# - https://docs.oracle.com/en/solutions/network-topology-oracle-database-at-aws/
# - https://aws.amazon.com/about-aws/whats-new/2025/12/oracle-database-aws-available-three-additional-regions/
# - https://www.oracle.com/news/announcement/oracle-database-at-aws-now-generally-available-2025-07-08/
service:
name: "Oracle Database@AWS"
also_known_as:
- "ADB Multicloud (AWS)"
- "ODB@AWS"
- "Oracle Database Service for AWS (legacy name)"
category: "Multicloud Database"
ga_date: "2025-07-08"
what: |
Oracle Database running on OCI Exadata infrastructure co-located inside
AWS datacenters. AWS apps connect via ODB peering (private, low-latency
network bridging AWS VPC to OCI infrastructure in the same AZ).
Control plane runs in OCI; data plane is physically in the AWS region.
Single invoice through AWS Marketplace. Usage counts toward AWS commitments.
services_available:
- name: "OCI Exadata Database Service on Dedicated Infrastructure"
versions: ["19c", "26ai"]
notes: "Full Exadata performance, RAC, Data Guard"
- name: "OCI Autonomous AI Database on Dedicated Exadata Infrastructure (ADB-D)"
versions: ["19c", "26ai"]
notes: "Autonomous Database on dedicated Exadata — NOT serverless"
- name: "OCI Autonomous Recovery Service"
notes: "Automated backup and recovery"
services_NOT_available:
- name: "Autonomous Database Serverless (ADB-S)"
reason: |
ADB-S is NOT available on Database@AWS. Only ADB on Dedicated
Exadata Infrastructure (ADB-D) is supported. This is a critical
distinction when designing architectures — if the customer
specifically needs ADB-S serverless, they must use native OCI
or connect via FastConnect/VPN.
# --- Regions ---
regions_ga:
- {aws_region: "us-east-1", name: "US East (N. Virginia)", ga_date: "2025-07-08"}
- {aws_region: "us-west-2", name: "US West (Oregon)", ga_date: "2025-07-08"}
- {aws_region: "us-east-2", name: "US East (Ohio)", ga_date: "2025-12-23"}
- {aws_region: "eu-central-1", name: "Europe (Frankfurt)", ga_date: "2025-12-23"}
- {aws_region: "ap-northeast-1", name: "Asia Pacific (Tokyo)", ga_date: "2025-12-23"}
- {aws_region: "ca-central-1", name: "Canada (Central)", ga_date: "2026-Q1"}
- {aws_region: "eu-west-1", name: "Europe (Ireland)", ga_date: "2026-Q1"}
- {aws_region: "ap-southeast-2", name: "Asia Pacific (Sydney)", ga_date: "2026-Q1"}
regions_planned:
- "US West (N. California)"
- "South America (São Paulo)"
- "Europe (London)"
- "Europe (Milan)"
- "Europe (Paris)"
- "Europe (Spain)"
- "Europe (Stockholm)"
- "Europe (Zurich)"
- "Asia Pacific (Hyderabad)"
- "Asia Pacific (Melbourne)"
- "Asia Pacific (Mumbai)"
- "Asia Pacific (Osaka)"
- "Asia Pacific (Seoul)"
- "Asia Pacific (Singapore)"
regions_planned_notes: "Oracle and AWS announced plans to expand to 20+ total regions"
# --- Network Architecture ---
network:
connectivity: "ODB Peering"
description: |
ODB peering creates a private, direct connection between an AWS VPC
and the OCI-managed ODB network inside the same AWS AZ. Traffic never
traverses the public internet. This is NOT a standard FastConnect —
it's a co-located, same-datacenter interconnect.
latency:
same_az: "~200-400 microseconds RTT (extrapolated from Database@Azure benchmarks)"
cross_az: "~1 ms+ (variable, must validate)"
cross_region: "Variable, depends on distance"
notes: |
Oracle does not publish official RTT benchmarks for Database@AWS.
Database@Azure (same architecture pattern) shows 200-400μs same-AZ
and ~1.5ms cross-AZ per Accenture testing (32,000+ tests, 2 weeks).
Database@AWS should be comparable since the architecture is identical
(co-located OCI infra inside cloud provider datacenter).
best_practices:
- "Deploy app EC2 and ODB network in the SAME Availability Zone"
- "Use Transit Gateway with attachment in same AZ as ODB network"
- "CIDR blocks must not overlap with AWS VPC subnets or OCI VCNs"
- "Client subnet minimum /27, recommended /24 for expansion"
- "Backup subnet minimum /28 (optional for ADB-D)"
- "Use Direct Connect for hybrid (on-premises) connectivity"
topologies:
- name: "Same-AZ Direct Peering"
use_case: "Latency-sensitive apps"
path: "App VPC → ODB Peering → ODB Network → Oracle DB"
recommendation: "Primary topology for low-latency workloads"
- name: "Hub-and-Spoke via Transit Gateway"
use_case: "Multi-VPC architectures"
path: "Spoke VPCs → Transit Gateway → ODB Network → Oracle DB"
caveat: "Cross-VPC latency varies — must validate"
- name: "Cross-Region via Transit Gateway Peering"
use_case: "Multi-region apps"
caveat: "Significant latency increase — not for latency-sensitive"
# --- Pricing ---
pricing:
model: |
Single invoice through AWS Marketplace.
- Exadata: Upfront subscription for infrastructure + pay-per-use for CPUs
- ADB-D: Upfront subscription + pay-per-use for active CPUs
aws_commitment: "Oracle Database@AWS usage counts toward AWS spending commitments"
# --- When to use vs alternatives ---
when_to_use:
- "App runs on AWS and needs Oracle Database with Exadata performance"
- "Customer wants single AWS bill (Marketplace billing)"
- "Low-latency (<1ms) app-to-DB connectivity required without migrating app"
- "Customer has AWS spending commitments to burn down"
- "Data residency requires DB to be in same region as app"
when_NOT_to_use:
- "Need ADB-S Serverless — use native OCI + FastConnect instead"
- "Target AWS region not yet GA — check availability"
- "Workload fits RDS Oracle or doesn't need Exadata performance"
- "Budget-sensitive: minimum Exadata infra commitment applies"
- "Need full OCI service breadth beyond database (OKE, Functions, etc.)"
# --- Gotchas ---
gotchas:
- id: "DBAWS-001"
severity: HIGH
issue: "ADB-S Serverless NOT available — only ADB-D Dedicated"
impact: |
Customers expecting serverless auto-scaling and pay-per-query will
need to use ADB-D with manual OCPU scaling, or use native OCI ADB-S
with FastConnect from AWS.
recommendation: |
If the customer specifically needs serverless, design with native
OCI ADB-S + FastConnect. If they need co-located low latency,
use ADB-D on Database@AWS and size Exadata appropriately.
- id: "DBAWS-002"
severity: MEDIUM
issue: "Minimum Exadata infrastructure commitment"
impact: |
Database@AWS requires dedicated Exadata infrastructure.
Minimum quarter-rack equivalent — not suitable for small workloads.
recommendation: |
For workloads < 16 OCPUs, evaluate if the latency benefit of
co-location justifies the Exadata minimum vs FastConnect to
native OCI ADB-S.
- id: "DBAWS-003"
severity: MEDIUM
issue: "VM clusters cannot be moved between ODB networks"
impact: "Once deployed in an AZ, the cluster stays there."
recommendation: "Choose the AZ carefully — align with app tier AZ placement."
- id: "DBAWS-004"
severity: LOW
issue: "Control plane runs in OCI region, not in AWS"
impact: |
Management operations (provisioning, patching, scaling) go through
OCI control plane. If OCI region has issues, management is affected
but data plane continues to serve queries.
recommendation: "Monitor both OCI and AWS health dashboards."
# --- Integration with AWS services ---
aws_integrations:
- "Amazon VPC (ODB peering)"
- "AWS IAM (federated access)"
- "Amazon CloudWatch (monitoring)"
- "Amazon EventBridge (events)"
- "Amazon S3 (data integration)"
- "AWS SageMaker / Bedrock (AI/ML via zero-ETL)"
- "AWS Transit Gateway / Cloud WAN (networking)"
- "AWS Direct Connect (hybrid connectivity)"

77
kb/services/dbcs.yaml Normal file
View File

@@ -0,0 +1,77 @@
---
last_verified: 2026-03-14
service: Database Cloud Service (DBCS)
category: database
oci_color: "#AA643B"
---
what: Oracle Database on VM or Bare Metal in OCI. Full DBA control with
automated provisioning and backup. Available as single-instance or 2-node RAC.
editions:
- Standard Edition
- Enterprise Edition
- Enterprise Edition High Performance
- Enterprise Edition Extreme Performance
when_to_use:
- Standard Edition workloads (ADB requires EE)
- Need full OS and database control without Exadata
- Moderate workloads that don't need Exadata performance
- Budget-conscious deployments where Exadata is over-provisioned
- Development and test environments mirroring production DB config
- Applications requiring specific Oracle versions or patches
when_NOT_to_use:
- High-performance OLTP (Exadata or ADB better)
- Variable workloads benefiting from auto-scaling (use ADB-S)
- No DBA team available (use ADB-S)
- Need Exadata features (Smart Scan, HCC, Flash Cache)
limits:
vm_shapes:
- "VM.Standard.E5.Flex: 1-94 OCPUs"
- "VM.Standard3.Flex: 1-32 OCPUs"
bm_shapes:
- "BM.Standard.E5: 128 OCPUs"
- "BM.DenseIO.E5: 128 OCPUs with NVMe"
max_storage_tb: 80 # block storage
rac_max_nodes: 2
features:
os_access: true
rac: "2-node RAC on VM shapes"
data_guard: true
cross_region_data_guard: true
custom_db_home: true
custom_patches: true
automated_backup: true
database_management: true
ha_dr:
local_ha: "2-node RAC for HA, single-instance with automated restart"
data_guard:
same_region: "Synchronous or async, FSFO available"
cross_region: "Asynchronous, manual or auto failover"
pricing:
model: per_ocpu_per_hour
vm_ocpu_payg: 0.1360 # per OCPU per hour (EE)
vm_ocpu_byol: 0.0680
bm_per_hour: "Fixed per shape"
storage: "Block Volume pricing applies"
notes:
- "VM shapes billed per enabled OCPU per hour"
- "BM shapes billed per hour for the full shape"
- "Storage is separate (Block Volume pricing)"
- "Backup storage at Object Storage rates"
gotchas:
- id: DBCS-001
issue: "2-node RAC is maximum on VM shapes"
impact: "Cannot scale RAC beyond 2 nodes (use ExaCS for more)"
recommendation: "If >2 RAC nodes needed, evaluate ExaCS"
- id: DBCS-002
issue: "Performance limited by block storage"
impact: "Cannot match Exadata IOPS/latency"
recommendation: "Use higher performance block volumes or move to ExaCS for I/O intensive workloads"

89
kb/services/dbexpert-api-reference.yaml Normal file
View File

@@ -0,0 +1,89 @@
---
last_verified: 2026-03-17
description: |
Oracle DBExpert public REST API reference for refreshing the database service catalog.
Use this to keep kb/services/dbexpert-catalog.yaml up to date.
---
# ── DBExpert ORDS REST API ─────────────────────────────────────────
swagger_ui: https://oracle-dbexpert.github.io/swagger/
base_url: https://apexadb.oracle.com/ords/dbexpert
endpoints:
all_db_services:
method: GET
url: https://apexadb.oracle.com/ords/dbexpert/db-services/v1/all
description: "Complete database service catalog with capabilities, multicloud, compliance"
response_format: JSON
fields_per_service:
- DATABASE_SERVICE_NAME
- DATABASE_TYPE # Single Database, Distributed, Consolidation Pool
- MANAGEMENT_MODEL # Fully Managed PaaS, Co-managed PaaS, Customer Managed
- SUPPORTED_CLOUD_ENVIRONMENTS
- RECOMMENDED_WORKLOADS
- RECOMMENDED_DATA_MODELS
- CERTIFIED_ORACLE_APPLICATIONS
- ORACLE_AI_DATABASE_BYOL_SUPPORT
- CPU_RANGE
- SHAPES
- CPU_SCALING # Online, Auto scale up/down
- STORAGE_SCALING
- MAX_IOPS
- MAX_THROUGHPUT
- MAX_MEMORY
- NINES_OF_AVAILABILITY # SLA/SLO
- ORACLE_DB_MAXIMUM_AVAILABILITY_ARCHITECTURE_MEDALS
- AUTOMATED_BACKUPS_MAX_RETENTION
- AZURE_COMPLIANCE
- GOOGLE_CLOUD_COMPLIANCE
- AWS_COMPLIANCE
- ALLOWS_SYSDBA_ACCESS
- SELECTAI_SUPPORT
- MONGO-COMPATIBLE_API
- SUPPORTED_DATABASE_VERSIONS
- AUTONOMOUS
- HARDWARE_INFRASTRUCTURE
- INCLUDED_ORACLE_DB_OPTIONS_FOR_LICENSE-INCLUDED_SERVICE
- FREE_ADD-ONS_(NO_EXTRA_LICENSING_REQUIRED)
- OCI_LOCATIONS
- ORACLE_DATABASE@AZURE_LOCATIONS
- ORACLE_DATABASE@GOOGLE_CLOUD_LOCATIONS
- ORACLE_DATABASE@AWS_LOCATIONS
- IS_AVAILABLE_AT_GOOGLE_CLOUD_(GCP)
- IS_AVAILABLE_AT_AZURE
- IS_AVAILABLE_AT_AWS
multicloud_regions:
url: https://apexadb.oracle.com/ords/r/dbexpert/multicloud-capabilities/multicloud-regions
description: "Multicloud region availability matrix (APEX app, WAF-blocked for curl)"
notes: "Must use browser or Swagger UI"
service_advisor:
url: https://apexadb.oracle.com/ords/r/dbexpert/dbsn/service-advisor
description: "Interactive service advisor/comparison tool (APEX app, WAF-blocked for curl)"
notes: "Must use browser"
dbsn_home:
url: https://apexadb.oracle.com/ords/r/dbexpert/dbsn/home
description: "Cloud Tools home page (APEX app)"
access_notes: |
- The REST API at /ords/dbexpert/db-services/v1/all is accessible from Swagger UI
but blocked by Akamai WAF when called from curl/Python/programmatic clients
- The APEX apps (multicloud-capabilities, dbsn) are fully WAF-blocked
- To refresh data: open Swagger UI, execute the endpoint, copy JSON response
refresh_procedure:
step_1: "Open https://oracle-dbexpert.github.io/swagger/"
step_2: "Find GET /db-services/v1/all and click 'Try it out' → 'Execute'"
step_3: "Copy the Response body JSON"
step_4: "Paste to Claude with instruction: 'actualiza kb/services/dbexpert-catalog.yaml con esto'"
alternative: |
curl -s 'https://apexadb.oracle.com/ords/dbexpert/db-services/v1/all' \
-H 'accept: application/json'
(may fail due to WAF — use browser if it does)
kb_target_file: kb/services/dbexpert-catalog.yaml
services_count: 35
last_data_date: 2026-03-17

679
kb/services/dbexpert-catalog.yaml Normal file
View File

@@ -0,0 +1,679 @@
---
last_verified: 2026-03-17
source: https://apexadb.oracle.com/ords/dbexpert/db-services/v1/all
swagger: https://oracle-dbexpert.github.io/swagger/
description: Oracle Database services catalog from DBExpert API. Comprehensive capabilities, multicloud availability, SLAs, workload recommendations, and compliance data.
refresh_command: "curl -s 'https://apexadb.oracle.com/ords/dbexpert/db-services/v1/all' -H 'accept: application/json'"
notes: |
API may be blocked by Akamai WAF from non-browser clients.
Use Swagger UI at https://oracle-dbexpert.github.io/swagger/ to test.
(A) = Azure colocated region, (G) = Google Cloud colocated region
---
# =============================================================================
# Fully Managed PaaS
# =============================================================================
fully_managed_paas:
- short_name: ATP Dedicated
full_name: Autonomous AI Transaction Processing on Dedicated Infrastructure
management_model: Fully Managed PaaS
cloud_environments: [OCI, AWS]
multicloud: { azure: false, gcp: false, aws: true }
autonomous: true
sla: "99.995"
maa_medals: [Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "2-21504"
max_storage_tb: 1572
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [OLTP, Mixed, AI/ML, JSON, Graph, Blockchain, IoT]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: LAK Dedicated
full_name: Autonomous AI Lakehouse on Dedicated Infrastructure
management_model: Fully Managed PaaS
cloud_environments: [OCI, AWS]
multicloud: { azure: false, gcp: false, aws: true }
autonomous: true
sla: "99.995"
maa_medals: [Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "2-21504"
max_storage_tb: 1572
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [DW, Analytics, Data Lake, AI/ML, Mixed]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: ATP Serverless
full_name: Autonomous AI Transaction Processing Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: true
sla: "99.995"
sla_note: "with Autonomous Data Guard"
maa_medals: [Silver, Gold]
cpu_unit: ECPU
cpu_range: "2-16128"
max_storage_tb: 393
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [OLTP, Mixed, Microservices, AI/ML, JSON, Graph, Blockchain, IoT]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: LAK Serverless
full_name: Autonomous AI Lakehouse Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: true
sla: "99.995"
sla_note: "with Autonomous Data Guard"
maa_medals: [Silver, Gold]
cpu_unit: ECPU
cpu_range: "2-16128"
max_storage_tb: 393
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [DW, Analytics, Data Lake, AI/ML, Mixed]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: AJD Serverless
full_name: Autonomous AI JSON Database Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: true
sla: "99.95"
maa_medals: []
cpu_unit: ECPU
cpu_range: "2-512"
max_storage_tb: 10
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [JSON, Document Store, Microservices, IoT]
byol_support: false
db_versions: ["26ai", "19c"]
- short_name: ADB-S Elastic Pool
full_name: Autonomous AI Database Serverless in an Elastic Pool
management_model: Fully Managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: true
sla: "99.995"
maa_medals: [Silver, Gold]
cpu_unit: ECPU
cpu_range: "128-16384"
max_storage_tb: 393
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [Multi-tenant SaaS, ISV, Consolidated workloads]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: ADB-D Elastic Pool
full_name: Autonomous AI Database Dedicated in an Elastic Pool
management_model: Fully Managed PaaS
cloud_environments: [OCI, AWS]
multicloud: { azure: false, gcp: false, aws: true }
autonomous: true
sla: "99.95"
maa_medals: [Silver]
cpu_unit: ECPU
cpu_range: "128-16384"
max_storage_tb: 1572
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [Multi-tenant SaaS, ISV, Consolidated workloads]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: Globally Distributed ATP-D
full_name: Globally Distributed Autonomous AI Transaction Processing
management_model: Fully Managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: true
sla: "99.995"
maa_medals: []
cpu_unit: ECPU
cpu_range: "2-16128"
max_storage_tb: 393
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Globally distributed OLTP, Sharded databases, Low-latency geo-distributed]
byol_support: false
db_versions: ["26ai", "19c"]
- short_name: NoSQL
full_name: NoSQL Database Cloud Service
management_model: Fully Managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.995"
sla_note: "99.999 with Global Active Tables"
maa_medals: []
cpu_unit: Serverless
cpu_range: serverless
max_storage_tb: unlimited
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [IoT, Mobile backend, Gaming, Ad-tech, Key-value, Document]
byol_support: false
db_versions: []
- short_name: MySQL HeatWave
full_name: MySQL Database Service with HeatWave
management_model: Fully Managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.99"
sla_note: "with High Availability"
maa_medals: []
cpu_unit: OCPU
cpu_range: "1-128"
max_storage_tb: 64
select_ai: false
mongo_api: false
open_source: true
recommended_workloads: [Web applications, SaaS, E-commerce, OLTP+Analytics, HeatWave ML/GenAI]
byol_support: false
db_versions: ["8.4", "8.0"]
# =============================================================================
# Co-managed PaaS
# =============================================================================
co_managed_paas:
- short_name: ExaDB-D
full_name: Exadata Database Service on Dedicated Infrastructure
management_model: Co-managed PaaS
cloud_environments: [OCI, Azure, GCP, AWS]
multicloud: { azure: true, gcp: true, aws: true }
autonomous: false
sla: "99.95"
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "16-24320"
max_storage_tb: 3924
select_ai: false
mongo_api: true
open_source: false
recommended_workloads: [Mission-critical OLTP, Large DW, Consolidation, EBS, RAC, Data Guard]
byol_support: true
db_versions: ["26ai", "19c", "12.2", "12.1", "11.2"]
- short_name: ExaDB-XS
full_name: Exadata Database Service on Exascale Infrastructure (ExaDB-XS)
management_model: Co-managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: false
sla: "99.95"
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "0-2000"
max_storage_tb: 300
select_ai: false
mongo_api: true
open_source: false
recommended_workloads: [Small-to-medium Exadata, Dev/Test on Exadata, Entry-level mission-critical]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: ExaDB-C@C
full_name: Exadata Database Service on Cloud@Customer
management_model: Co-managed PaaS
cloud_environments: [Cloud@Customer]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.95"
sla_note: SLO
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "16-24320"
max_storage_tb: 3924
select_ai: false
mongo_api: true
open_source: false
recommended_workloads: [Data sovereignty, Regulated industries, Latency-sensitive on-prem, EBS]
byol_support: true
db_versions: ["26ai", "19c", "12.1", "11.2"]
- short_name: BaseDB SE
full_name: Base Database Service - Standard Edition - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "1-8"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Small departmental, Dev/Test, Non-critical OLTP]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB EE
full_name: Base Database Service - Enterprise Edition - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "1-64"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Enterprise OLTP, Mixed workloads, Moderate DW]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB EE HP
full_name: Base Database Service - Enterprise Edition High Performance - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "1-64"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Enterprise OLTP with partitioning, Advanced compression, OLAP]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB EE EP
full_name: Base Database Service - Enterprise Edition Extreme Performance - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: OCPU
cpu_range: "1-128"
cpu_note: "RAC up to 128 OCPUs across 2 nodes"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Mission-critical OLTP, RAC, Data Guard, In-Memory, Active Data Guard]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB SE - ECPU
full_name: Base Database Service - Standard Edition - ECPU
management_model: Co-managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: ECPU
cpu_range: "4-32"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Small departmental, Dev/Test, Non-critical OLTP, Multicloud]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB EE - ECPU
full_name: Base Database Service - Enterprise Edition - ECPU
management_model: Co-managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: ECPU
cpu_range: "4-256"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Enterprise OLTP, Mixed workloads, Multicloud]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB EE HP - ECPU
full_name: Base Database Service - Enterprise Edition High Performance - ECPU
management_model: Co-managed PaaS
cloud_environments: [OCI, Azure, GCP]
multicloud: { azure: true, gcp: true, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: ECPU
cpu_range: "4-256"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Enterprise OLTP with partitioning, Advanced compression, Multicloud]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: Globally Distributed ExaDB-XS
full_name: Globally Distributed Exadata Database on Exascale Infrastructure
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.95"
sla_note: SLO
maa_medals: []
cpu_unit: ECPU
cpu_range: "0-2000"
max_storage_tb: 300
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Globally distributed databases, Sharded Exadata, Geo-distributed OLTP]
byol_support: true
db_versions: ["26ai"]
- short_name: PostgreSQL
full_name: Oracle Cloud Infrastructure Database with PostgreSQL
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.99"
sla_note: "with multi-node HA"
maa_medals: []
cpu_unit: OCPU
cpu_range: "2-64"
max_storage_tb: 64
select_ai: false
mongo_api: false
open_source: true
recommended_workloads: [PostgreSQL workloads, Open source migration, Web applications]
byol_support: false
db_versions: ["15", "14"]
- short_name: LAK-ExaC@C
full_name: Autonomous AI Lakehouse on Dedicated Infrastructure Cloud@Customer
management_model: Co-managed PaaS
cloud_environments: [Cloud@Customer]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: true
sla: "99.995"
maa_medals: [Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "2-21504"
max_storage_tb: 1572
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [Data sovereignty DW, On-prem analytics, Regulated data lake]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: ATP-ExaC@C
full_name: Autonomous AI Transaction Processing on Dedicated Infrastructure Cloud@Customer
management_model: Co-managed PaaS
cloud_environments: [Cloud@Customer]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: true
sla: "99.995"
maa_medals: [Silver, Gold, Platinum]
cpu_unit: ECPU
cpu_range: "2-21504"
max_storage_tb: 1572
select_ai: true
mongo_api: true
open_source: false
recommended_workloads: [Data sovereignty OLTP, On-prem mission-critical, Regulated workloads]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB Arm EE
full_name: Base Database Service Arm - Enterprise Edition - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "2-80"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Cost-optimized Enterprise, Arm-native workloads]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB Arm EE EP
full_name: Base Database Service Arm - Enterprise Edition Extreme Performance - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: OCPU
cpu_range: "2-160"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Cost-optimized mission-critical, Arm RAC, Arm Data Guard]
byol_support: true
db_versions: ["26ai", "19c"]
- short_name: BaseDB Arm EE HP
full_name: Base Database Service Arm - Enterprise Edition High Performance - VM
management_model: Co-managed PaaS
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: "99.9"
sla_note: SLO
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "2-80"
max_storage_tb: 40
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Cost-optimized with partitioning, Arm advanced compression]
byol_support: true
db_versions: ["26ai", "19c"]
# =============================================================================
# Customer Managed
# =============================================================================
customer_managed:
- short_name: IaaS Bare Metal
full_name: OCI Compute - Bare Metal
management_model: Customer Managed
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: null
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "64-192"
max_storage_tb: unlimited
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Full OS control, Custom RAC, Legacy versions, Bare-metal performance]
byol_support: true
db_versions: ["26ai", "19c", "12.2", "12.1", "11.2"]
- short_name: IaaS VM
full_name: OCI Compute - Virtual Machine
management_model: Customer Managed
cloud_environments: [OCI]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: null
maa_medals: [Bronze]
cpu_unit: OCPU
cpu_range: "1-94"
cpu_note: "E6.Flex up to 126 OCPUs"
max_storage_tb: unlimited
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [Dev/Test, Custom config, Legacy versions, Full OS control]
byol_support: true
db_versions: ["26ai", "19c", "12.2", "12.1", "11.2"]
- short_name: Exadata DB Machine
full_name: Oracle Database on Exadata Database Machine (on-prem)
management_model: Customer Managed
cloud_environments: [On-Premises]
multicloud: { azure: false, gcp: false, aws: false }
autonomous: false
sla: null
maa_medals: [Bronze, Silver, Gold, Platinum]
cpu_unit: Cores
cpu_range: "0-2880"
max_storage_tb: unlimited
select_ai: false
mongo_api: false
open_source: false
recommended_workloads: [On-prem Exadata, Air-gapped, Full hardware control]
byol_support: true
db_versions: ["26ai", "19c", "12.2", "12.1", "11.2"]
# =============================================================================
# Always Free & Developer Editions
# =============================================================================
always_free_and_developer:
- short_name: ATP Serverless - Always Free
full_name: Autonomous AI Transaction Processing Serverless - Always Free
base_service: ATP Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI]
autonomous: true
cpu_unit: ECPU
cpu_range: "2"
max_storage_tb: 0.02
select_ai: true
mongo_api: true
db_versions: ["26ai", "19c"]
notes: "Always Free tier, 20 GB storage, no SLA"
- short_name: LAK Serverless - Always Free
full_name: Autonomous AI Lakehouse Serverless - Always Free
base_service: LAK Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI]
autonomous: true
cpu_unit: ECPU
cpu_range: "2"
max_storage_tb: 0.02
select_ai: true
mongo_api: true
db_versions: ["26ai", "19c"]
notes: "Always Free tier, 20 GB storage, no SLA"
- short_name: AJD Serverless - Always Free
full_name: Autonomous AI JSON Database Serverless - Always Free
base_service: AJD Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI]
autonomous: true
cpu_unit: ECPU
cpu_range: "2"
max_storage_tb: 0.02
select_ai: true
mongo_api: true
db_versions: ["26ai", "19c"]
notes: "Always Free tier, 20 GB storage, no SLA"
- short_name: ADB-S Developer
full_name: Autonomous AI Database Serverless - Developer
base_service: ATP Serverless
management_model: Fully Managed PaaS
cloud_environments: [OCI]
autonomous: true
cpu_unit: ECPU
cpu_range: "2-512"
max_storage_tb: 10
select_ai: true
mongo_api: true
db_versions: ["26ai", "19c"]
notes: "Developer edition, reduced cost, non-production use"
- short_name: BaseDB Arm Developer
full_name: Base Database Service Arm - Developer Edition - VM
base_service: BaseDB Arm EE
management_model: Co-managed PaaS
cloud_environments: [OCI]
autonomous: false
cpu_unit: OCPU
cpu_range: "2-80"
max_storage_tb: 40
select_ai: false
mongo_api: false
db_versions: ["26ai", "19c"]
notes: "Arm Developer edition, non-production use"
# =============================================================================
# Quick-reference: Multicloud availability matrix
# =============================================================================
# Service | OCI | Azure | GCP | AWS | C@C
# -------------------------|-----|-------|-----|-----|----
# ExaDB-D | Y | Y | Y | Y |
# ExaDB-XS | Y | Y | Y | |
# ATP Dedicated | Y | | | Y |
# LAK Dedicated | Y | | | Y |
# ATP Serverless | Y | Y | Y | |
# LAK Serverless | Y | Y | Y | |
# AJD Serverless | Y | Y | Y | |
# ADB-S Elastic Pool | Y | Y | Y | |
# ADB-D Elastic Pool | Y | | | Y |
# BaseDB SE/EE/HP - ECPU | Y | Y | Y | |
# ExaDB-C@C | | | | | Y
# LAK-ExaC@C / ATP-ExaC@C | | | | | Y
# All others | Y | | | |

102
kb/services/exacs.yaml Normal file
View File

@@ -0,0 +1,102 @@
---
last_verified: 2026-03-14
service: Exadata Cloud Service (ExaCS)
category: database
oci_color: "#AA643B"
---
what: Full Oracle Exadata system in OCI. Provides OS access, RAC, full DBA control
with cloud elasticity. Runs the same Exadata software as on-prem.
when_to_use:
- Need OS-level access for custom agents, scripts, or compliance tools
- RAC required for application architecture
- Sustained high OCPU workloads (>128 OCPUs)
- Lift-and-shift from on-prem Exadata with minimal changes
- Need custom database parameters not available in ADB
- Applications that use features incompatible with ADB (e.g., dblinks to non-Oracle)
when_NOT_to_use:
- Small/medium workloads (over-provisioned)
- No DBA team (ExaCS requires database administration)
- Variable workloads that benefit from ADB auto-scaling
- Budget-constrained (high minimum commitment)
limits:
shapes:
- name: "Exadata.Quarter3.100"
base_ocpu: 100
max_ocpu: 100
storage_tb: 49.5
- name: "Exadata.Half3.200"
base_ocpu: 200
max_ocpu: 200
storage_tb: 99
- name: "Exadata.Full3.400"
base_ocpu: 400
max_ocpu: 400
storage_tb: 198
max_vm_clusters: 8
max_databases_per_cluster: "Limited by resources"
max_pdb_per_cdb: 252
features:
os_access: true
rac: true
data_guard: true
cross_region_data_guard: true
custom_db_home: true
custom_patches: true
grid_infrastructure: true
flash_cache: true
smart_scan: true
storage_compression: true
hybrid_columnar_compression: true
ha_dr:
local_ha: "RAC across Exadata nodes, automatic failover"
data_guard:
same_region: "Synchronous, automatic failover with FSFO"
cross_region: "Asynchronous or far-sync, manual or automatic failover"
sizing_rules:
minimum: "Quarter rack (100 OCPUs base)"
scaling: "Can enable additional OCPUs in increments"
storage: "Comes with infrastructure, expandable"
pricing:
model: infrastructure_plus_ocpu
infrastructure_monthly: "Fixed per shape"
enabled_ocpu_per_hour: 0.336 # approximate
byol_ocpu_per_hour: 0.168
notes:
- "Infrastructure cost is fixed per shape"
- "Only enabled OCPUs are billed"
- "BYOL provides ~50% discount on OCPU portion"
- "Storage included with infrastructure"
gotchas:
- id: EXACS-001
issue: "Provisioning takes hours to days"
impact: "Cannot provision on-demand like ADB-S"
recommendation: "Plan capacity well in advance"
- id: EXACS-002
issue: "Minimum quarter rack commitment"
impact: "Significant base cost even at low utilization"
recommendation: "Ensure sustained usage justifies the infrastructure cost"
- id: EXACS-003
issue: "DBA team required for ongoing operations"
impact: "Patching, tuning, and maintenance are customer responsibility"
recommendation: "Ensure DBA team capacity before choosing ExaCS over ADB"
- id: EXACS-004
issue: "Scale-down requires VM cluster modification"
impact: "Not as elastic as ADB-S for variable workloads"
recommendation: "Right-size for steady-state, not peak"
migration_tools:
- name: Oracle Data Guard
use_for: "On-prem Exadata to ExaCS with minimal downtime"
- name: RMAN Restore
use_for: "Backup-based migration with planned downtime"
- name: Zero Downtime Migration (ZDM)
use_for: "Automated physical migration"

101
kb/services/exadata-cloud.yaml Normal file
View File

@@ -0,0 +1,101 @@
# OCI Service: Exadata Cloud Service (ExaCS)
# Last verified: 2026-03
service:
name: "Exadata Cloud Service (ExaCS)"
id: exacs
category: database
color: "#AA643B"
description: "Dedicated Exadata infrastructure running in OCI, providing the full performance and isolation of Exadata hardware with cloud elasticity. Supports Oracle RAC, Data Guard, and direct OS/CDB-level access for maximum DBA control."
when_to_use:
- "Oracle RAC workloads requiring multi-node clustering"
- "Regulatory or compliance scenarios demanding dedicated infrastructure isolation"
- "High IOPS / low-latency database workloads (OLTP or mixed)"
- "Sustained compute needs exceeding 128 OCPUs"
- "Need direct OS-level or CDB-level access for custom patching, tuning, or agents"
when_not_to_use:
- "Small workloads under 16 OCPUs — use Autonomous Database Serverless (ADB-S) or Base Database Service"
- "No dedicated DBA team to manage patching, RAC, and infrastructure"
- "Simple OLTP with no RAC or isolation requirements — use ADB-S instead"
- "Dev/test environments where cost efficiency matters more than performance"
variants:
- id: exacs_x9m
name: "ExaCS X9M"
description: "Exadata X9M shape — current-generation infrastructure with RDMA over Converged Ethernet and persistent memory acceleration."
- id: exacs_x10m
name: "ExaCS X10M"
description: "Exadata X10M shape — next-generation infrastructure with improved compute, storage density, and throughput."
sizing:
rack_configurations:
quarter_rack:
ocpus: "100 (scalable)"
memory: "1.44 TB"
storage: "Up to 76.8 TB usable (Exadata Storage)"
db_nodes: 2
storage_servers: 3
half_rack:
ocpus: "200 (scalable)"
memory: "2.88 TB"
storage: "Up to 153.6 TB usable"
db_nodes: 4
storage_servers: 6
full_rack:
ocpus: "400 (scalable)"
memory: "5.76 TB"
storage: "Up to 307.2 TB usable"
db_nodes: 8
storage_servers: 12
ocpu_scaling: "OCPUs can be scaled online in increments without downtime. You pay for enabled OCPUs, not the total available in the rack."
sizing_guidance: "Start with a quarter rack for most production workloads. Scale OCPUs on demand. Choose half/full rack only when storage capacity or aggregate memory requirements exceed quarter rack limits."
gotchas:
- id: exacs_minimum_cost
severity: HIGH
description: "Minimum infrastructure cost is approximately $6,000+/month for a quarter rack, regardless of OCPU usage. Ensure sustained workload justifies the commitment."
- id: exacs_provisioning_time
severity: MEDIUM
description: "Exadata infrastructure provisioning takes 4-8 hours. Plan deployments accordingly — this is not an instant resource like a Compute VM."
- id: exacs_patching_window
severity: MEDIUM
description: "Patching requires a scheduled maintenance window. Database nodes are patched in a rolling fashion but plan for reduced capacity during the process."
- id: exacs_gi_db_patch_separate
severity: MEDIUM
description: "Grid Infrastructure (GI) and Database Home patches are applied separately and may have different schedules. Coordinate both to avoid version skew."
- id: exacs_overprovisioning_risk
severity: HIGH
description: "Customers frequently over-provision by choosing half or full racks when a quarter rack with OCPU scaling would suffice. Always validate actual IOPS and CPU requirements before sizing up."
- id: exacs_network_placement
severity: LOW
description: "ExaCS requires placement in a private subnet with sufficient IP addresses. Each DB node and each virtual IP consumes an IP; plan your subnet CIDR accordingly."
implied_dependencies:
- service: vcn
reason: "ExaCS infrastructure must be deployed in a VCN"
- service: private_subnet
reason: "DB nodes and SCAN listeners require private subnet placement"
- service: service_gateway
reason: "Access to OCI object storage for backups and patching from private subnets"
- service: oci_vault
reason: "TDE wallet management and encryption key storage"
competitive_notes:
vs_aws: "AWS has no equivalent dedicated Oracle Exadata infrastructure offering. RDS Oracle and RDS Custom lack RAC support and Exadata storage acceleration. Customers needing true Exadata performance have no AWS-native path."
references:
documentation: "https://docs.oracle.com/en-us/iaas/Content/Database/Concepts/exaoverview.htm"
pricing: "https://www.oracle.com/cloud/price-list/#exadata"
changelog:
- date: "2026-03-14"
contributor: { name: "Diego Cabrera", team: "Field Architecture" }
change: "Initial creation with shapes, sizing, gotchas, dependencies"

91
kb/services/networking.yaml Normal file
View File

@@ -0,0 +1,91 @@
---
last_verified: 2026-03-14
service: OCI Networking
category: networking
oci_color: "#4F7B6E"
---
what: Software-defined networking layer in OCI. Includes VCN, subnets, gateways,
load balancers, DNS, and connectivity options.
components:
vcn:
what: "Virtual Cloud Network — isolated network in OCI"
cidr: "Supports multiple CIDR blocks, /16 to /30"
max_per_region: 50
subnet:
what: "Subdivision of VCN, can be regional (spans all ADs)"
types: ["public", "private"]
recommendation: "Always use private subnets for databases and app servers"
security_list:
what: "Stateful firewall rules at subnet level"
recommendation: "Prefer NSGs (Network Security Groups) for granular control"
nsg:
what: "Network Security Group — firewall rules at VNIC level"
recommendation: "Preferred over security lists for micro-segmentation"
internet_gateway:
what: "Enables internet access for public subnets"
nat_gateway:
what: "Enables outbound internet for private subnets"
service_gateway:
what: "Private access to OCI services (Object Storage, ADB, etc.)"
recommendation: "Always use for database and storage access — no internet traversal"
drg:
what: "Dynamic Routing Gateway — hub for VCN peering and on-prem connectivity"
supports: ["VCN peering", "FastConnect", "IPSec VPN", "Remote peering"]
load_balancer:
types:
- name: "Flexible Load Balancer"
what: "Layer 7 (HTTP/HTTPS) load balancer"
bandwidth: "10 Mbps to 8 Gbps (flexible)"
- name: "Network Load Balancer"
what: "Layer 4 (TCP/UDP) load balancer"
bandwidth: "Up to line rate"
connectivity:
fastconnect:
what: "Dedicated private connection to OCI (like AWS Direct Connect)"
speeds: ["1 Gbps", "2 Gbps", "5 Gbps", "10 Gbps", "100 Gbps"]
redundancy: "Always deploy 2 circuits for HA"
notes: "Partner or co-location model, typical setup takes 2-4 weeks"
ipsec_vpn:
what: "Encrypted tunnel over internet"
bandwidth: "Up to 250 Mbps per tunnel, aggregate with multiple tunnels"
notes: "Good for dev/test or backup connectivity, not production data transfer"
vcn_peering:
local: "Within same region, no bandwidth limits"
remote: "Cross-region via DRG, standard inter-region latency"
pricing:
vcn: "Free"
subnet: "Free"
nat_gateway_per_hour: 0.0084
service_gateway: "Free"
drg_per_hour: 0.016
fastconnect:
port_per_month:
1gbps: 180
10gbps: 680
data_ingress: "Free"
data_egress: "Free over FastConnect"
load_balancer:
flexible_base: 0.014 # per hour
per_mbps: 0.0013
notes:
- "Inter-region data transfer: $0.0085/GB"
- "Internet egress: first 10 TB/month free, then $0.0085/GB"
- "OCI egress pricing is significantly cheaper than AWS/Azure/GCP"
gotchas:
- id: NET-001
issue: "VCN CIDR blocks cannot overlap for peering"
impact: "Plan CIDR ranges carefully for multi-VCN architectures"
recommendation: "Use a documented IP addressing scheme before deployment"
- id: NET-002
issue: "FastConnect provisioning takes 2-4 weeks with partners"
impact: "Can delay migration timelines"
recommendation: "Start FastConnect procurement early, use VPN as interim"
- id: NET-003
issue: "Security lists apply to entire subnet, NSGs to specific VNICs"
impact: "Security lists can be too broad for micro-segmentation"
recommendation: "Use NSGs as primary, security lists as fallback"

97
kb/services/oci-networking-core.yaml Normal file
View File

@@ -0,0 +1,97 @@
# OCI Service: OCI Networking Core (VCN, Subnets, Gateways)
# Last verified: 2026-03
service:
name: "OCI Networking Core"
id: networking_core
category: infrastructure
description: "Foundational networking bundle covering Virtual Cloud Networks (VCN), subnets, and gateways. Every OCI deployment depends on these components for connectivity, segmentation, and traffic routing."
components:
- name: "Virtual Cloud Network (VCN)"
id: vcn
description: "Software-defined private network in OCI. Provides the IP address space, DNS, and route table framework for all attached resources."
when_to_use:
- "Required for every OCI deployment — compute, database, Kubernetes, and managed services all reside in a VCN"
- name: "Subnet (Public)"
id: public_subnet
description: "Subnet where instances can receive public IP addresses and are reachable from the internet via an Internet Gateway."
when_to_use:
- "Load balancers, bastion hosts, or resources that must accept inbound internet traffic"
- "Dev/test instances needing direct internet access"
- name: "Subnet (Private)"
id: private_subnet
description: "Subnet with no public IP assignment. Resources communicate outbound via NAT Gateway and access OCI services via Service Gateway."
when_to_use:
- "Application servers, databases, and backend services that should not be internet-facing"
- "Any workload subject to security or compliance restrictions on public exposure"
- name: "Internet Gateway (IGW)"
id: igw
description: "Provides a path for inbound and outbound internet traffic to/from resources in public subnets."
when_to_use:
- "Public-facing load balancers or bastion hosts need internet connectivity"
- name: "NAT Gateway"
id: nat_gateway
description: "Enables outbound-only internet access for resources in private subnets. No inbound initiation from the internet."
when_to_use:
- "Private subnet resources need to pull OS patches, container images, or call external APIs"
- name: "Service Gateway"
id: service_gateway
description: "Private pathway from a VCN to supported OCI services (e.g., Object Storage, Autonomous Database) without traffic traversing the internet."
when_to_use:
- "Any private subnet workload that needs to reach OCI Object Storage, streaming, or other supported services"
- "Backup traffic from databases or compute that should stay on the Oracle backbone"
- name: "Dynamic Routing Gateway (DRG)"
id: drg
description: "Virtual router that connects a VCN to on-premises networks (via FastConnect or IPSec VPN), other VCNs, or remote regions."
when_to_use:
- "Hybrid cloud connectivity to on-premises data centers"
- "VCN-to-VCN peering across regions or tenancies"
- "Hub-and-spoke network topologies"
- name: "Local Peering Gateway (LPG)"
id: lpg
description: "Connects two VCNs in the same region for private traffic exchange without traversing the internet or a DRG."
when_to_use:
- "Intra-region VCN-to-VCN peering when a DRG hub is not needed"
- "Simple two-VCN peering scenarios"
design_rules:
- "Allocate a /16 CIDR block per VCN to allow room for future subnet expansion"
- "Plan CIDR ranges for growth — adding non-overlapping CIDRs later is supported but the original CIDR cannot be changed"
- "Avoid CIDR overlap with on-premises networks and other VCNs that will be peered"
- "Create separate subnets per tier (web, app, database) and per availability domain when needed for fault isolation"
- "Prefer Network Security Groups (NSGs) over Security Lists — NSGs are attached to individual resources and are easier to manage at scale"
gotchas:
- id: vcn_cidr_immutable
severity: HIGH
description: "A VCN's original CIDR block cannot be modified or removed after creation. Additional non-overlapping CIDRs can be added, but plan the initial range carefully."
- id: security_rule_limit
severity: MEDIUM
description: "Each security list supports a maximum of 200 rules (ingress + egress combined). For complex environments, use multiple NSGs instead of overloading a single security list."
- id: service_gateway_required
severity: HIGH
description: "Resources in private subnets cannot reach OCI services (Object Storage, Autonomous Database, etc.) without a Service Gateway and corresponding route rule. This is a common misconfiguration."
- id: drg_required_hybrid
severity: MEDIUM
description: "A DRG is required for FastConnect, IPSec VPN, and cross-VCN peering via transit routing. Plan DRG attachment early — retrofitting routing later adds complexity."
references:
documentation: "https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/overview.htm"
vcn_best_practices: "https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/bestpractices.htm"
changelog:
- date: "2026-03-14"
contributor: { name: "Diego Cabrera", team: "Field Architecture" }
change: "Initial creation with VCN, subnets, gateways, DRG design rules and gotchas"

45
kb/services/oci-queue.yaml Normal file
View File

@@ -0,0 +1,45 @@
---
last_verified: 2026-03-14
service: OCI Queue
category: integration
oci_color: "#6B4D9A"
---
what: Fully managed serverless message queue. Supports standard queue semantics
with at-least-once delivery, visibility timeout, and dead letter queues.
when_to_use:
- Decoupling microservices
- Work distribution across consumers
- Buffering requests during traffic spikes
- Simple pub/sub messaging without Kafka complexity
when_NOT_to_use:
- Need strict ordering (use OCI Streaming)
- Need real-time streaming analytics (use OCI Streaming)
- Need message replay (use OCI Streaming)
- Complex routing/filtering (use OCI Streaming or third-party)
limits:
max_message_size_kb: 512
max_retention_days: 7
max_queues_per_compartment: 100
max_channels_per_queue: 10
max_visibility_timeout_hours: 12
features:
dead_letter_queue: true
visibility_timeout: true
long_polling: true
batched_operations: true
encryption_at_rest: true
private_endpoint: true
pricing:
model: per_request
per_million_requests: 0.40
data_transfer: "Standard OCI egress pricing"
notes:
- "No minimum commitment"
- "Billed per API request (send, receive, delete)"
- "Very cost-effective for moderate throughput"

74
kb/services/oke.yaml Normal file
View File

@@ -0,0 +1,74 @@
# OCI Service: Oracle Container Engine for Kubernetes (OKE)
# Last verified: 2026-03
service:
name: "Oracle Container Engine for Kubernetes (OKE)"
id: oke
category: infrastructure
color: "#2D5967"
description: "Managed Kubernetes service with Oracle-optimized control plane, integrated with OCI networking, IAM, and observability."
when_to_use:
- "Containerized applications (microservices, 12-factor apps)"
- "Need horizontal auto-scaling for application tier"
- "Multi-team environments needing namespace isolation"
- "CI/CD-driven deployments"
- "Workloads requiring service mesh, ingress controllers"
when_not_to_use:
- "Simple stateless functions → use OCI Functions instead"
- "Single monolithic app with no container strategy → use Compute VMs"
- "Team has no Kubernetes experience and timeline is tight"
- "Batch processing only → consider OCI Data Flow or Compute"
variants:
- id: oke_managed
name: "OKE Managed Nodes"
description: "Customer manages worker nodes (OS patching, scaling config)"
- id: oke_virtual
name: "OKE Virtual Nodes"
description: "Serverless worker nodes — no OS management, pay per pod"
use_when:
- "Want zero node management overhead"
- "Bursty workloads with variable pod count"
- "Cost optimization for intermittent workloads"
sizing:
control_plane: "Free (managed by Oracle)"
worker_nodes:
recommended_shapes:
- "VM.Standard.E4.Flex (general purpose, best price/performance)"
- "VM.Standard.A1.Flex (ARM/Ampere, 30-50% cheaper for compatible workloads)"
- "VM.Standard3.Flex (Intel, when Intel compatibility required)"
- "VM.GPU.A10.1 / VM.GPU.A100 (GPU workloads)"
sizing_guidance: "Start with 3 nodes across fault domains for HA. Size OCPUs based on aggregate pod CPU requests + 20% headroom."
gotchas:
- id: oke_lb_shape
severity: LOW
description: "OKE creates OCI Load Balancers for LoadBalancer-type services. Default is 10 Mbps flexible — adjust annotation for production bandwidth."
- id: oke_cni_choice
severity: MEDIUM
description: "VCN-Native Pod Networking (OCI CNI) gives pods VCN IPs directly — better for NSG integration but consumes subnet IPs. Flannel overlay is simpler but no direct VCN integration."
- id: oke_pv_block_volume
severity: LOW
description: "Persistent volumes use OCI Block Volumes. For ReadWriteMany, use OCI File Storage (FSS) CSI driver."
implied_dependencies:
- service: vcn
reason: "Worker nodes and pods need VCN subnets"
- service: load_balancer
reason: "Ingress traffic to services"
- service: block_storage
reason: "Persistent volumes for stateful pods"
references:
documentation: "https://docs.oracle.com/en-us/iaas/Content/ContEng/home.htm"
changelog:
- date: "2026-03-14"
contributor: { name: "Diego Cabrera", team: "Field Architecture" }
change: "Initial creation with managed/virtual nodes, sizing, gotchas, dependencies"

70
kb/services/storage.yaml Normal file
View File

@@ -0,0 +1,70 @@
---
last_verified: 2026-03-14
service: OCI Storage Services
category: storage
oci_color: "#4F7B6E"
---
what: OCI storage services including Block Volume, Object Storage, File Storage,
and Archive Storage.
services:
block_volume:
what: "Network-attached block storage for compute instances"
performance_tiers:
- name: Lower Cost
iops_per_gb: 2
throughput_kbps_per_gb: 240
- name: Balanced
iops_per_gb: 60
throughput_kbps_per_gb: 480
- name: Higher Performance
iops_per_gb: 75
throughput_kbps_per_gb: 600
- name: Ultra High Performance
max_iops: 450000
max_throughput_mbps: 2680
max_volume_size_tb: 32
max_volumes_per_instance: 32
object_storage:
what: "S3-compatible object storage"
tiers:
- name: Standard
use_for: "Frequently accessed data"
- name: Infrequent Access
use_for: "Data accessed less than once per month"
- name: Archive
use_for: "Long-term retention, compliance"
retrieval_time: "1 hour (standard), 1 minute (expedited)"
features:
- "S3-compatible API"
- "Versioning"
- "Lifecycle policies"
- "Server-side encryption (SSE)"
- "Replication (same-region and cross-region)"
max_object_size_tb: 10
file_storage:
what: "NFSv3-compatible managed file system"
use_for: "Shared file access across multiple compute instances"
max_size: "8 EB (exabytes)"
iops: "Up to 25,000 IOPS per file system"
throughput: "Up to 1.2 GB/s per mount target"
pricing:
block_volume:
balanced_per_gb_month: 0.0255
higher_performance_per_gb_month: 0.0340
uhp_per_gb_month: "Varies by VPU"
object_storage:
standard_per_gb_month: 0.0255
infrequent_per_gb_month: 0.0100
archive_per_gb_month: 0.0026
api_per_10k_requests: 0.0034
file_storage:
per_gb_month: 0.0340
notes:
- "Block Volume: first 200 GB free (boot volume)"
- "Object Storage: first 10 GB free, 50k API requests free"
- "Data transfer to Object Storage: free (within region)"