Background In dotnet-architecture/eShopOnWeb I noticed the interesting usage of Specification classes. When I did some digging, I found that these are implemented through ardalis/Specification For those who are more familiar with the Java world we have Data Specifications. If you read Implementing Domain Driven design in the bibliography you find a reference to Martin Fowlers paper. Sample based on Wikipedia So if we look at Wikipedia we can infer the following code: public class OverDueSpecification :[...]

As previously mentioned in the blog I use a M1 mac. In order to help introduce others to Kubernetes I have done some testing of the K8S tutorial. In order to try it out I first tried using the qemu driver for minikube. First gotcha was that the image gcr.io/google-samples/kubernetes-bootcamp:v1 does not work on ARM natively. Let the Yac Shaving begin Running minikube in docker In order to get around this limitation you can run minikube in docker. Either by using colima or Docker Desktop with experimen[...]

Project with many repositories This is a continuation of Monorepo versus Polyrepo. This is a story about a project I worked on. We had some pain points related to many different source repositories. Shared business domain library that contained shared business types Shared library with a base parent entity (with common behavior) Many services that dealt with different subdomains that uses a few shared libraries Very complicated requirements with lots of nuances Different persons had different[...]

In 2021 my aging MacBook Pro (16GB RAM, I7) had issues with a swelling battery. The touch pad sensitivity became an issue. In order to replace that machine I opted for a MacBook Air (8GB, M1). Compilation speed (at least of F# code) on the Air is faster than the old machine, but it is not as responsive when I have a lot of things running at the same time. In order to try out and showcase different technologies and services, I usually run Docker. Most images that I used where fine, however the one image th[...]

This post is a continuation of Unclean architecture. Clean architecture From what I understand of Clean architecture it’s an iteration of Hexagonal architecture also known as Ports and Adapters (see the Wikipedia page). Clean architecture use of OO and code dependency OO is the ability, through the use of polymorphism, to gain absolute control over every source code dependency in the system. It allows the architect to create a plugin architecture, in which modules that contain high-level policies ar[...]