Functional vs. Non-Functional Requirements

Separating what a system must do (features such as search, cart and payments) from how well it must do it (latency, availability, consistency, scalability) before designing it.

Core Idea

(To be expanded)

Key Principles

(To be added)

Examples

(To be added)

Connections

(To be added)

Source

Extracted from How To Build Recommendation Algorithms And System Designs