Skip to main content

Finding the right balance: Simplification vs Optimization

Maybe you don’t care, but there is a reason I named my blog the ‘Art of Simplicity’. As an application architect I always think about the following quotes when building out an architecture

“Simplicity is the ultimate sophistication.” — Leonardo da Vinci

“Perfection is Achieved Not When There Is Nothing More to Add, But When There Is Nothing Left to Take Away” – Antoine de Saint-Exupery

“Everything should be made as simple as possible, but not simpler.” – Albert Einstein

As an architect I see it as my job to find the right balance between simplification and optimization.

I’ve been in situations where a quick and dirty change will haunt us forever but I’ve also seen the opposite where so called ‘best practices’ introduced an endless list of layers of indirection(facades that call services that call factories that call builders and so on…)  where no one has a clue what’s going on.

The best architectures are the ones were the solution is as simple as possible, but not simpler. What makes getting there even harder is that according to the following post(Simplifiers vs Optimizers) is that people have a natural tendency to either be an optimizer or a simplifier.

What kind of person are you?

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...