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

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         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

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.