Banksalad Publishes Go Coding Conventions… Presents Panic Prevention and Error Handling Principles

Banksalad's Core Backend Team defined organization-wide coding conventions based on its 4 years of experience developing services using Go and gRPC. While Go has a low barrier to entry, the key is maintaining conceptual consistency using lint tools such as golangci-lint to prevent misuse.

Panic and Error Handling Principles

In production runtime, panic is not used for exception handling, and is restricted to fail-fast purposes only at initialization time. To guard against unintended panics, a recovery chain is added to server interceptors or middleware, and a PanicSafeGroup struct is implemented and used to ensure the safety of goroutines created inside handlers. For error handling, stack traces are preserved using tools such as errors.WithStack, and it is recommended that errors inside defer statements not be ignored but logged instead.

Data Structures and String Handling

For slice and map usage, nil slice is recommended, and the len() function is used to determine emptiness. Since Go does not guarantee order when iterating over maps, either sort is applied for result stability, or iteration itself is avoided. To prevent errors caused by byte-level access when iterating over strings, the for i, rune := range s approach is used, and utf8.RuneCountInString is used to check character counts.