|
Post by rubina9898 on Dec 24, 2023 11:19:48 GMT
Records ADR A particularly valuable form of documentation is Architecture Decision Records ADR . ADR documents describe important architectural decisions made in a project in a given context and with the consequences of these decisions. A good ADR has the following features contains the reason for making the decision for example the choice of a database engine for an application can be justified by the need to store user data one. ADR should cover one decision contains the time of creation explains the decision made in the context of business requirements includes Phone Number List alternative solutions along with the reason for rejecting them as well as the strengths of the alternative solutions. Templates and examples of ADR documents can be found at the end of the article in links to sources and additional materials. Dependency update. This is a seemingly unimportant topic that if neglected may cause major problems in the long run. Outdated dependencies primarily expose the application to attacks using vulnerabilities found in the outdated dependency. The second problem resulting from outdated dependencies is the act of updating them. Let's assume that the project is several years old and the dependencies have never been updated. Some of them have received many updates and while updating dependencies one version higher will probably not take too much time updating several dozen versions higher may result in a large and unexpected amount of work.
|
|