Skip to main content

On avoiding ‘big bang’ rewrites

I encounter too much organizations where they move from one ‘big bang’ rewrite to another.

The situation always evolves in the same way:

A new system is created that will replace an old system. But this time we’ll do it right. We throw out all the old technology and choose the latest and greatest shiny tools. After a few months/years/decades the new system finally sees the light and it looks awfully similar to the old system(although the user interface is a little better). This ‘new’ system over time becomes harder and harder to maintain. Adding new functionality costs more and more until we arrive at the moment where developers throw in the towel and declare it became impossible to add any new feature or change. It’s time for the next rewrite…

Does this sounds familiar?

A smart man once said:

“The definition of insanity is doing the same thing over and over and expecting different results.”

The mistake that is made is that the team focusses too much on the technology and they’ll handle it as a technical migration. As a consequence you’ll end up with the same system written in a more modern(better?) technology without really improving the system.

The solution? Don’t do a rewrite, instead focus on evolutionary architecture and apply the strangler pattern to evolve from the old to the new system.

The universe was created with one big bang, since then it is continuously evolving We wouldn’t like it to have the universe evolve with a next big bang, as we’ll not survive the event.

So why we think it’s a valid approach for our systems?

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

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...