Code Freely, Live Fully
Code Freely, Live Fully
Introduction I have been programming web backends for longer than I care to remember. Up until recently, I used C# extensively because it came closest to the sweet spot I was looking for: a language that was relatively easy to…
Introduction One of Go’s main selling points, at least for me, is its support for concurrency. Starting a go routine is almost ridiculously easy, and channels make communication between go routines a breeze. However, as the saying goes, with great…
Introduction In this article I discussed the implementation of the Abstract Factory pattern. The Factory Method is simply an extension of that pattern. Creating an object can sometimes be complex. A factory-method can abstract this complexity away, and let subclasses…
Introduction The prototype-pattern is a creational design pattern that allows us to create new objects by cloning existing ones, i.e. the existing objects function as a kind of template. This can save time in some cases when for example an…
Introduction The flyweight pattern is a pattern that helps minimize memory usage by sharing and reusing data. A common example is wordprocessor where each character not only holds the character like ‘A’ but also things like markup and formatting data.…
Introduction Go is known for its simplicity and clarity, but when it comes to managing state or creating reactive data flows, developers often have to write a lot of boilerplate. With the introduction of generics in Go 1.18, new patterns…
Introduction Many times when writing concurrent code, the need arises to protect a certain resource, or resources from concurrent access. A way of doing this is by using the Monitor pattern. Implementing this pattern usually involves the use of the locks…
Introduction The Bridge pattern is a design pattern that is meant to “decouple an abstraction from its implementation so the two can vary independently”. To that end this pattern can use encapsulation, aggregation and also inheritance in order to separate…
Sometimes creating an object is expensive, either an object takes up a lot of resources, or costs time to initialize because of external dependencies, like web services or databases. Then it might be a good idea to construct the object…
Introduction Dependency Injection is simply said, the idea that your classes should depend on abstraction, i.e. the abstraction of a datasource for example, rather than on concrete implementations. This means that classes will depend on interfaces rather than on real…
Introduction In Design Patterns, the Iterator is a way of traversing over a container, that is access each of the container’s elements. It is used as a convenient way to traverse over lists or arrays, but it could also be…
Introduction On this page I described building a simple web API with a Postgres database at the backend. For this I used the Gin web framework which is pretty fast in itself. A nice extension however would be to use…
Introduction The Decorator pattern can be used to dynamically alter or add functionality to existing classes. This pattern is oftern more efficient than subclassing because it relieves us of the need of defining a new object. So, what does it…
Introduction The Chain of Responsibility (CoC) pattern describes a chain of command/request receivers. The client has no idea which one of the receivers will handle the request. The beauty of the pattern is again uncoupling: the sender and the receiver…
Introduction The facade pattern is used as a way to hide more complex logic. A facade can do the following: A facade pattern is typically used in the following cases: What does it look like? Well, it is quite simple:…