Hooray! This is the last post of the “Simplify!” series. As I wrote before: I would never have expected that it would become that long. Initially, I expected 4, maybe 5 parts. Most likely I would not have dared to begin with it if I would have known. Anyway, we have arrived here – at last!

In the previous post, I discussed several relevant drivers that lead to ever-increasing complexity of the IT landscape, creating layers over layers of technology over time that never get cleaned up. As the post would have become too long otherwise, I left out the mitigation options.

In the previous post, I discussed several drivers of accidental complexity on the implementation level and what we can do about it.

In the previous post, I completed the consideration of accidental complexity at the architecture level by discussing potential countermeasures to the drivers of accidental complexity which I discussed in the post before.

This post is about mitigation techniques regarding accidental complexity in the architectural level.