Common non-functional requirements
Non-functional requirements aid in balancing the trade-offs between various features, guiding the design and methodology according to what’s essential for the target audience and the intended use of the API. It establishes a norm for the behavior of the API.
Often referred to as quality attributes, non-functional requirements (NFRs) are the standards that evaluate a system’s functionality rather than its particular behaviors or functions.
Each architect has a set of NFRs that they need to manage. These NFRs outline a solution’s technical limitations and specify how it should operate. The most common NFRs are availability, scalability, performance, security, observability, maintainability, resiliency, reliability, consistency, and quality.
Some NFRs, such as scalability, high availability, fault tolerance, and disaster recovery, will be discussed in Chapter 16. In this chapter, we will be discussing some of the NFRs related...
