Building a Firecracker VM Orchestrator in Go - Part 2: API Server
go
dev.to
Introduction If you missed the first post in this series, start here. It covers the foundation: five provider interfaces that decouple the Flames control plane from any specific infrastructure backend. This time we're building the first thing that actually does something: the API server. This is the first real consumer of those provider interfaces. A running binary. go run ./cmd/flames-api, curl against it, create a VM. That kind of thing. But what made this spec interesting wasn't