Code Freely, Live Fully
Code Freely, Live Fully
Introduction When we build programs that do many things at once, we want to make sure they’re secure. Go is a modern language that is really good at keeping things safe in memory but still works really fast. One big…
Introduction The composite pattern allows you treat a group of objects like a single object. The objects are composed into some form of a tree-structure to make this possible. This patterns solves two problems: We do this by doing the…
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 Abstract Factory Pattern is a way to group the creation of related objects, like products of a certain brand or make by building a common factory interface. If this all sounds abstract, a picture can help: A short…
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 Most applications require business rules, such as data validation. It’s crucial to implement these rules in a way that’s flexible, clear, and easy to maintain. The Specification pattern offers a solution, allowing the creation of reusable business rules that…
Introduction In another article we discussed the Lock pattern. In this we used the sync.Mutex struct. The problem with this struct is, is that it doesn’t distinguish between reading from a resource, like accessing an element in a vector, and writing…
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 Sometimes in a multi-threaded program, there is a need to protect a resource from concurrent access, that is access by multiple threads. One way of doing this is by implementing a Monitor Object. Implementing this pattern usually involves the…
Introduction There are many ways to handle incoming events. If you need to be able to handle many potential service requests concurrently, the Reactor pattern could be your pattern of choice. The key ingredient of this pattern is a so-called…
Introduction In some applications it is handy not to say necessary for the main thread (or a thread) to wait for the completion of several worker threads. Examples of these kinds of problems are: There are probably many other use…
Introduction Sometimes when locking data or objects it can be handy to reduce the overhead of acquiring a lock on such objects by first checking whether a lock is really necessary. This typically used in combination with lazy initialization in…
Introduction Especially in multi-threaded applications it can be necessary to synchronize properties between objects, or at least be notified of changes on certain properties. This is where the Binding Properties comes in, which is basically a form of the Observer…