// APIs

Manually maintaining SDKs across multiple programming languages is slow, error-prone, and a constant drag on developer velocity. This episode—featuring developer advocate Steve Kuching—explores using the open-source OpenAPI Generator to automate SDK creation from an OpenAPI spec, deploying the generator as a containerised service, and observing the entire pipeline with OpenTelemetry auto-tracing and Lumigo. Learn how to apply the same build, test, and observe principles you use for services to your SDK generation pipeline.

Chris and Matt pick up inside GitHub Codespaces, getting the Player State service running locally on the first attempt thanks to Dapr's environment-variable secret store and Codespaces secrets. They then wire up the World Events Engine with Azure Storage Queue bindings and Table Storage state before hitting a stubborn .NET minimal API routing bug — becoming the cliffhanger that sets up the next session.

Chris and Matt wire up Dapr state management for their .NET player state service, configure VS Code debugging for multi-service development, and document game use cases covering player enrollment, world event ticks, and decision lifecycle.

Chris and Matt refactor their Go player decisions API, restructuring packages and project layout. They compare the Gin and Gorilla Mux HTTP frameworks, explore Go interfaces and dependency injection patterns, and discuss unit testing and mocking strategies in Go.

Chris and Matt dive into Go (Golang) for the first time on stream, building a player decisions REST API for their game project. They explore Go fundamentals including structs, pointers, packages, and the Gin HTTP framework while comparing Go patterns to C# and .NET conventions.

In this post, I show how I use GitHub Actions to call an Azure Function (through Azure API Management) that interacts with Google Analytics as part of the process to build my Hugo Static Site. The end result is that top posts are pulled into the Static Site Generation build process, rather than calling the Google Analytics API through JavaScript at runtime.

Chris and Matt build the world events engine in .NET, connecting it to the Player State models via project references. They design a state machine architecture for the game engine, discuss action points as a game mechanic, and plan the player decisions API in Go for the next episode.

APIs are the glue that connect rich user experiences to our data and services. Good governance using tools such as API Management are vital. Join us as we explore how to work with the deployment options for APIs in Azure API Management and how these can be integrated in CI/CD pipelines. This first episode is particularly suitable for Architects and Developers interested in applying Infrastructure as Code skills to APIs.

APIs are the glue that connect rich user experiences to our data and services. Good governance using tools such as API Management are vital. Join us as we explore how to work with the deployment options for APIs in Azure API Management and how these can be integrated in CI/CD pipelines. This first episode is particularly suitable for Architects and Developers interested in applying Infrastructure as Code skills to APIs.

Chris and Matt start building the Player State API using .NET Web API, defining data models for the SpaceBar management sim game. They scaffold the project, discuss minimal APIs versus controller-based approaches, and set up a GitHub Actions CI workflow to build and validate the service on every commit.