While I do not have a great understanding of Software Architecture as much as I do with programming the Backend of that same software, I still take into appreciation the looks of its design. When I took sight of “The top 5 software architecture patterns: How to make the right choice” written by Freelance writer Peter Wayner, one of the things that was eye-catching was how the Software Architecture Patterns were described throughout this blog. While the Microservices Architecture was one of the only architectures that I had familiarized myself with while reading through the different architectures, I had been more interested in the endless vacuum of strengths that the Space-based architecture had when seeing the benefits that it poses. The article had given a very understanding of all the Software Architectures by showing their strengths and their weaknesses, making it easier to see where their limits are foreseen.
I chose this article since I searched far and wide for a topic that I least understood, but still would be inspired to follow through reading about it for fulfillment. The article does a really great job at grabbing the reader, as the most complex part about trying to understand a Software Architecture is when you are trying not to break your own code with a Software Architecture that poses a great risk in causing your program to crash unexpectedly. For the simplicity of the reader, Wayner had given either a telling example or a visualization that would help the reader have a simple explanation of what the structure is designed to do for your program as its structure.
The biggest takeaway I had after reading this article was that I was still able to learn that each architecture shapes your program in a way to help better understand what to do with your program next. However, Software Architecture is still only the beginning of what you need to do to fully design your software. A software may still need changes that an architecture alone cannot fix, but what an architecture should do is help you see the full picture of your own work that you have done. A Software Architecture is only a frame in the end, but the program you create would be best suited for an environment that is needed to put it on full display.
https://techbeacon.com/app-dev-testing/top-5-software-architecture-patterns-how-make-right-choice
From the blog CS@Worcester – Elias' Blog by Elias Boone and used with permission of the author. All other rights reserved by the author.