DEV Community

Cover image for Golang Patterns - Part 1
Nicola Apicella
Nicola Apicella

Posted on • Updated on

Golang Patterns - Part 1

Hi everyone!
Today's objective is to describe and document a bunch of golang patterns.

As you know from my previous posts (go concurrency and go lambdas), I have recently entered the Go-land and found out quite soon that common idioms I knew from my previous experience did not quite apply to golang.

Well, I found out that there are some patters that are so common that in my humble opinion should be presented as part of any beginner guide about golang.
All the code in the examples is on github.

Group constants

The title said it all, we want to group common constants in the same namespace.


A chain of suppliers that returns as soon as one of the suppliers returns a non-zero result or an error.
The code shows an example in which we need to load a configuration value from one of the possible sources: env variable, config file or a database.
We want to stop searching for the config value as soon as a non-zero result is returned.

Code for the chain here.


Options shows a flexible way to construct an object.
The major benefit is being able to add more parameters in the future to the object constructor without breaking the clients.
In other languages, you would probably use an overloaded constructor or fall back to the builder pattern.

Code for the option here.


Maybe is a container which may or may not contain a non-null value.

Function type

Functions are first class citizen in Golang. They can be used as a type whenever we want to easily implement a Strategy pattern or similar.
This pattern is heavily used in the golang http package.


Thanks for reading!

Let me know if you found it useful and if there is a key pattern that should really be part of this list.

Top comments (2)

msoedov profile image
Alex Miasoiedov • Edited

we want to group common constants in the same namespace.

This does not quite fit all use cases, this constants package introduces an inter package/module dependency which not always great especially in service oriented envs

Options shows a flexible way to construct an object.

Actually is relatively harder to read and implement comparing to building pattern


napicella profile image
Nicola Apicella

Hi! Thanks for the feedback. I named the package after the example I wanted to show (I.e. maybe package, options package etc.). It is not required to have the constants in a different package (neither is required to name it constants in case you want to have a different package).
As for Options, it s a really valid point and I think the reason why options is more popular than builder(despite the fact that builder is slightly more readable) may be the lack of library like Lombok for example, which generates boiler plate code for you. Options is a bit more light from this point of view, but like you pointed out, might loose a bit in readability.