Architecture Best Practices

Over the years of my work as a software developer and architect, I have repeatedly observed that in the field of software architecture, we seek new standards and solutions with every project and are always reinventing the wheel. Just as Andie MacDowell and Bill Murray experience it in the movie “Groundhog Day”, we practice software architecture. We start out ignorant, not knowing, and work our way forward. Trial and error.

And our learning path is paved with projects that reflect our level of knowledge and our mistakes. This does not mean that we have not been successful with what we have done in detail. And even if the project has failed, this often has nothing to do with the software architecture and technology. In most cases, it is often a question of social interaction within the project and the organization carrying out the project.

But that shouldn’t stop us from getting better in the area of software architecture and falling back on tried and tested solutions. That is why I have started to compile my own experience from the last few decades on this site.

My initial motivation was to write down all the knowledge for myself so that I could easily access it myself and share it with others. Instead of writing down the same solution over and over again and explaining it to other people, I just want to be able to send a link to one of these pages from this area. I would like to be able to exchange technical information with all the steakholders involved more quickly.

I cannot and will not claim to be absolute, nor would I claim that there are no better approaches to certain problems. But if this work helps us to become a little better and achieve the goals we have a little more relaxed, then this page has achieved its goal.