We often define cloud-native in terms of Kubernetes, service meshes, and orchestration platforms. But cloud-native software does not begin with a cluster.

It begins at main().

In this talk, we will build a production-grade Go service from scratch and examine what truly makes it cloud-native. No frameworks. No YAML. Just deliberate design decisions made in application code.

We will explore graceful shutdown, signal handling, structured logging, health endpoints, context propagation, timeouts, concurrency boundaries, and observability — all implemented directly using Go’s standard library. Along the way, we will uncover a deeper idea: cloud-native is not a platform feature. It is an architectural mindset.

Go’s philosophy — explicit error handling, lightweight concurrency, context-driven cancellation, and static binaries — naturally encourages resilient, restartable, observable systems. These traits are what allow software to thrive in distributed, failure-prone environments.

By the end of this session, you will understand how to design services that behave predictably under orchestration without depending on orchestration. You will leave with concrete patterns you can apply immediately, whether your service runs in Kubernetes, on a VM, or as a single binary on a small device.

Cloud-native does not start in YAML.
It starts in main().