Designing and Planning a Cloud Solution Architecture

Fully managed and serverless services (e.g., Cloud Run, BigQuery, Cloud SQL, Spanner) that shift patching, scaling, and availability work to Google.

So that trade-offs (cost, availability, speed) can be justified against what the business actually values, and over-engineering is avoided.

Build (custom) what differentiates the business, like the recommendation engine, and buy SaaS for commodity capabilities such as payroll and email.

A functional requirement states what the system must do (e.g., process an order); a non-functional requirement states how well it must do it (availability, latency, security, scalability, cost).

Functional: it describes a capability the system must provide.

Non-functional (performance/latency). It constrains how well the system behaves, not what it does.