If you are a Software Architect (or even a Solutions or Enterprise Architect for that matter) you’ll come across one important problem that you need to master, day in day out. Making choices and decisions on which technologies to use in your projects; be it in your corporate context, startup, personal projects, and whatnot.
In this post I’m going to touch upon a few key aspects an architect should consider and look into in making technology selections. By no means this is an exhaustive list of points that an architect needs to consider. There are numerous other factors to consider in this regard. However, the points I discuss stand out the most. Also, these facts are not new, but a few known facts that we might just not think enough. I’m more than happy to learn any other crucial aspects that architects must and do consider in choosing technologies.
Today, the technology is fast changing at a rapid pace that you probably hear new emerging JavaScript frameworks every now and then. During the last decade, the industry has brought in new trends, reference architectures, programming languages, DevOps tools, and whatnot. Some decade-old technologies are still going strong. Choices are countless. Architects have to make decisions every day.
You would also have come across battles on various topics; Angular or React, open-source or…
