Skip to main content
Miraj Abeysekara
OpenChoreo Maintainer @ WSO2
View all authors

How to Build an Internal Developer Platform on Azure with OpenChoreo

· 17 min read
Miraj Abeysekara
OpenChoreo Maintainer @ WSO2
Janaka Sandaruwan
OpenChoreo Maintainer @ WSO2

Azure gives teams the infrastructure to run applications. But infrastructure alone doesn't tell developers how to get a service into production: where to register it, how to request a database, which environments they can deploy to, and where to look when something fails. Platform teams need to make those steps consistent across services while keeping control over the infrastructure underneath.

For platform engineers already running workloads on AKS, the remaining work is turning Azure services into a self-service path for developers. OpenChoreo, an open-source developer platform, is one way to build that path on top of what the team already runs.

Provisioning Resources in OpenChoreo with Crossplane

· 13 min read
Miraj Abeysekara
OpenChoreo Maintainer @ WSO2

OpenChoreo can provision managed infrastructure, such as databases and caches, through Crossplane. In our post on self-service resources, we described how a ResourceType can point at whatever provisioner a platform team already uses, Crossplane included. The new Crossplane integration is a working example of that. It provisions PostgreSQL and Redis through Crossplane v2, and its ResourceTypes and Compositions are ready to try as they are, or to copy and adapt for your own platform.

There is more than one way to put Crossplane behind a ResourceType. The integration takes one opinionated position: the data plane decides how a resource is built. This post walks through the options, the trade-offs of the one we picked, and the contract between OpenChoreo and Crossplane that makes it work.

Self-Service Databases, Queues, Caches, and Other Resources in OpenChoreo

· 12 min read
Miraj Abeysekara
OpenChoreo Maintainer @ WSO2

OpenChoreo v1.1 shipped recently, and one of the headline features is resource abstractions: a way to treat managed infrastructure like databases, queues, and caches as first-class, declarative dependencies of a workload. Platform engineers publish reusable ResourceType templates. Developers self-serve a Resource from one of those templates (picking the type, filling in only the parameters they care about) and wire its outputs into their Workload, the same way they already reference other components' endpoints.

This post walks through the model, the new CRDs that back it, and a real example you can install: a small collaborative document editor called Doclet that depends on Postgres and NATS.