Software Architecture Series
It has been quite a while since I last posted on my blog. My futile attempt to reinvigorate my writing died out very quickly due to personal circumstances. Study always likes to interfere with these kind of things, so does work.
Since everything has become more stable, I feel like I can pick up my blog again. However, I don’t want to fall into the same pit as I did earlier this year. So, I came up with a plan, and it is genius! (As always, what else would you expect from me?! :P)
Ever since my internship, I got an increasing interest in software architectures. Don’t ask me why; I cannot tell you because I don’t even know why myself. During my internship, I had to design software from scratch and thus did some research into software architectures. That research showed me the importance of architecture in software. However, since I’m now working as a software tester, I also see the importance of understanding software architecture for tester and how it can impact their work as well.
Hence, I decided I’d create a series on my blog on software architectures. In this series, I want to explain the importance of software architectures for multiple disciplines that are involved in the development of new and old software. Furthermore, I’d like to go over a couple architectures in more detail ranging from the most popular (like the n-tier) to the lesser known (versioned services) architecture. But knowing all these architectures won’t get you anywhere without knowing how to decide which one to use for a project properly. That’s why I’ll also be explaining how I go about making a decision regarding the software architecture for a project.
During the upcoming weeks, I’ll try my best to post on a regular basis. If you have any questions or suggestions, be sure to leave a comment, and I’ll take a look into it.