golang-design-patterns

Functional options in Go enable scalable constructors with built-in validation by passing configuration functions to a struct. This pattern lets you set optional parameters like HTTP server timeouts while keeping defaults maintainable and explicitly initialized.

Using runtime.AddCleanup is recommended over SetFinalizer for resource management in Go. It provides a more predictable mechanism for associating cleanup functions with objects, preventing resource leaks and hidden bugs without relying on garbage collector finalization timing.

Avoiding init functions in Go promotes explicit initialization for better testability. Hidden side effects during package initialization lead to unmaintainable code and obscure bugs, whereas explicit setup allows developers to control state and dependencies clearly during runtime.

Bounded channel pools in Golang manage resource limits by allocating a fixed number of resources through a buffered channel. This pattern ensures graceful shutdown by draining the channel and releasing resources safely, preventing leaks during application termination.

Golang enums should start at 1 and include an unknown sentinel value to avoid zero-value bugs. Because Go initializes unassigned integers to zero, starting enums at 1 ensures the default zero value represents an explicitly unassigned state rather than a valid enum.

Choosing between hexagonal and clean architecture in Go depends on right-sizing your application's complexity. Hexagonal architecture isolates business logic from infrastructure using ports and adapters, while clean architecture layers dependencies, both preventing unmaintainable code in growing projects.