Making decisions about software architecture always has been difficult. That's even more true today with the growing number of options and the increasing complexity of systems. How can you make this process easier?
In this video, Grygoriy Gonchar talks about a simple framework for making and documenting software architecture decisions. The goal is to follow a process that provides good input for decision-making, creates actionable guidance based on those decisions, and documents the decisions so that it is easy to understand why they have bee made.
In a nutshell, the process uses three main ingredients that are based on established practices, but combines them in a specific and nicely complementary way:
👉 Technology Radars: Track and understand the technology landscape to make informed decisions about which technologies to use.
👉 Technology Standards: Ensure consistency of crosscutting concerns and reduce the risk of suboptimal adoption of new technologies.
👉 Architectural Decision Records (ADRs): Capture decisions and provide a historical record of their reasoning.
If you are interested in more details, here is the original article that describes the decision-making and documentation process:
👉 @infoq: A Simple Framework for Architectural Decisions - [ Ссылка ]
#api #strategy #softwarearchitecture #softwareengineering #gettingapistowork #digitaltransformation
