The flyweight pattern is a design pattern I am not seeing that often in code bases but can be a good design pattern to reduce memory. The core idea is to initialize objects an share them as often as possible for reuse. Mostly the flyweight pattern can be seen in desktop UI implementation (GUI). In Java Swing, for instance, the JTable rendering uses this pattern, to reduce the computation needed for painting.

There are a number of design patterns I am using on daily bases, and one of them is the Singleton pattern. In Golang penalties in performance are not so harsh as in other languages, if the application is not designed and written to perform with minimal CPU and memory footprint. I’m trying to keep my implementations as performing as possible, but sometimes explicit benchmarks can revile the details. The singleton pattern is widely used in Object Oriented languages, and it is well worth to use it in golang.

This post is a walkthrough on my approach to develop and deploy Golang web service in Docker container. There are many reasons for integrating Docker into the daily routine as a developer, one being the simplification of setting up a separated runtime environment. Using containers in production has, even more, advantages from simplified release to better performance. Kubernetes and Docker Swarm is gaining more and more space, which I think is partly because of the simplified management on IBM Cloud and Google Cloud Platform.

I am always really excited reading peoples notes about new languages and technologies, and this was not different with Golang. I read about the language and an implementation roughly 4 years ago. After reading the article I looked around to find more details about the background of the language, and I was quiet surprised how much effort Google did put into this language. For this very reason the language was always on my “look into if I can” list.