Code Freely, Live Fully
Code Freely, Live Fully
Introduction Sometimes, for reasons of efficiency, it can be quite handy to keep a pool, that is non-empty set, of initialized objects ready. This can be the case in for instance when you have database connections, which are expensive to…
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 my previous post I compared the performance of Actix with Rust and Fiber with Go. However, this was not entirely fair, since for one I did not use connection pooling in the Fiber part. Let us see, two…
Introduction A couple of weeks ago I came across a well-written article by Mayank Choubey, where he did a performance comparison between a Web API written in Go using the Fiber framework and the Actix framework written in Rust. In…
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 singleton pattern restricts the instantiation of a class to a single instance. The singleton pattern makes it possible to ensure that: One of the main uses of the singleton pattern is logging, as all clients who wish to…
Introduction The command pattern is a behavioral design pattern. It is used by an Invoker to perform one action or a series of actions on objects, called Receivers. The Invoker is unaware of the nature of the receiving objects, it…
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:…
Introduction The Interpreter pattern can be used to interpret and evaluate sentences in a language. The idea is to make a class for each symbol, both terminal and non-terminal and construct a syntax tree which can be evaluated and interpreted.…
Introduction The mediator pattern is a pattern used when you want to simplify communication i.e. message dispatching in complex applications. It involves building a mediator where each objects can delegate its communication, and which routes the messages to the right…
Introduction The memento pattern can be used to (partially) expose the internal state of an object. One use case for this pattern is to serialize an object to a file or as JSON for example, another is to build an…