Enterprise cloud platform

The problem

A multi-environment cloud platform needed environments that could be created and recreated reliably rather than assembled by hand, with deployment automated across development, QA, demo and production.

The solution

Infrastructure as code in Pulumi over Microsoft Azure, CI/CD through GitHub Actions and Azure DevOps, containerised development environments, and application changes to support running the same codebase across multiple isolated environments — including database migration, PostgreSQL deployment, authentication and configuration, Azure networking and DNS, and deployment identities.

Technical implementation

Current enterprise engineering work for a US client, building and improving a multi-environment cloud and software platform on Azure. The client is not named here.

Technical implementation

The centre of the work is repeatability. An environment that was assembled by hand is an environment nobody can confidently rebuild, and that uncertainty ends up shaping every decision around it. Defining the infrastructure in Pulumi turns an environment into something reviewable, reproducible and disposable.

On top of that:

• repeatable Azure environments for QA, demo and production
• CI/CD through GitHub Actions and Azure DevOps, with repository and workflow configuration to match
• automated cloud deployments using deployment identities rather than long-lived secrets
• application changes so the same codebase runs correctly across multiple isolated environments, which is usually where configuration assumptions surface
• database migration work, including PostgreSQL deployment and migration
• containerised development environments, so a developer machine resembles the target
• Azure networking and DNS, authentication and configuration

The application side spans .NET services with Angular and React frontends, Azure Functions, Service Bus, PostgreSQL and SQL Server, with identity through Auth0 and Microsoft Entra ID.

The engagement is ongoing.