Salesforce ArchitectureBeginnernfrperformancescale
What are non-functional requirements (NFRs) on Salesforce projects?
Real World Scenario
App works for 50 users but crawls at 5,000. You explain NFRs beginners overlook.
Expected Answer
• NFRs cover performance, availability, security, compliance, and maintainability—not just features
• Examples: page load under 3 seconds, 99.9% uptime integration, GDPR retention policy
• Governor limits and API caps are platform NFR constraints architects design around
• Document expected data volumes and concurrent users early
• Test NFRs in full sandbox with realistic data shape, not empty orgs
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Large Data Volume—millions of records requiring selective queries, indexing, and async patterns. Changes design choices.
Architect Perspective
Feature list without NFRs is half a design—say that calmly in architecture interviews.