Three-Layer Architecture
Independent Terraform states for infrastructure, foundation operators, and application stacks — each with its own lifecycle and blast radius.
OSDU SPI Infrastructure
Terraform + Helm on AKS Automatic — Azure PaaS for data, in-cluster for compute.
What is this?
Section titled “What is this?”Infrastructure as Code for deploying the OSDU Azure SPI (Service Provider Interface) on AKS Automatic. A single azd up command provisions Azure PaaS resources, bootstraps cluster operators, and deploys the full OSDU service stack.
Azure PaaS + In-Cluster
CosmosDB, Service Bus, and Storage for data durability. Elasticsearch, Redis, and PostgreSQL in-cluster for fast provisioning and low cost.
AKS Automatic
Managed Istio, Cilium networking, Deployment Safeguards, and Karpenter node auto-provisioning — hardened by default with no additional configuration.
One Command Deploy
Azure Developer CLI orchestrates all layers through lifecycle hooks. azd up to deploy, azd down to tear down.
Architecture at a Glance
Section titled “Architecture at a Glance”| In-Cluster | Azure PaaS |
|---|---|
| Elasticsearch (search/indexer) | CosmosDB (SQL + Gremlin) |
| Redis (caching) | Azure Service Bus (messaging) |
| PostgreSQL via CNPG (Airflow metadata) | Azure Storage (blob/table) |
| Airflow (workflow orchestration) | Azure Key Vault (secrets) |
| Istio service mesh (managed by AKS) | Azure Container Registry |
| Application Insights |
Who is it for?
Section titled “Who is it for?”Platform Engineers deploying OSDU on Azure — stand up a running instance with azd up, tear it down with azd down.
Service Developers who need their own OSDU environment to code against, deploy to, and test with.