What is SOSL	What is SOQL
Salesforce Object Search Language (SOSL) is a Salesforce search language that is used to perform text searches in records. Use SOSL to search fields across multiple standard and custom object records in Salesforce.	Salesforce Object Query Language (SOQL) is similar to the SELECT statement in the widely used Structured Query Language (SQL) but is designed specifically for Salesforce data.
Best Practices Use targeted, specific search terms	Best Practices 1) Use Selective Filters 2) Index fields 3) Work with Salesforce to see if skinny tables would work for your use case 4) Avoid != in filters 5) Consider using Bulk API with bulk query.

Bulkify	Sharing and Row Locks	Governor Limits
Use appropriate API (Bulk v/s Soap)	Multiple disparate integrations that modify the same records cause issues	Design keeping Limits in mind
Best Practices 1) Bulkify in Apex code, especially triggers and web services 2) API – consolidate multiple API calls if possible 3) Bulk – Optimize batch size to avoid time-outs and limit retries	Best Practices 1) Do not use an active user for data integration 2) Use System.runAs() in Apex to ensure the correct user is used 3) Defer Sharing Calculations when appropriate	Best Practices 1) Choose the right integration pattern (sync v/s async) 2) Consider business SLA and business needs while designing integration pattern 3) Decide if data needs to reside inside or outside the platform

Filters & Scope	Number of Records	Reporting Governance
Efficient filters and operators help faster access and less data returned	Number of Records a user may have access to, consider the effects of Sharing	Ensure repeatable process around maintenance of list views and reports
Best Practices 1) Try using relative date values, e.g. THIS WEEK, NEXT MONTH, etc. 2) “Not-contains” and != prevent indexes from being used 3) “equal” is better than “contains” , which uses implicit wildcard	Best Practices 1) If the user has “View All” perm such as admin, try to add more selective indexed filters. 2) For certain mid-level users, it would be more useful to use “My Team” instead of “All” in the filter so that only records that can be seen through the role hierarchy will be fetched.	Best Practices 1) Segment users into groups per specific analytics requirements and use cases 2) Canned reports per user group with good filters 3) Review and cleanup unused dashboards and reports

Data Load	Performance Test Strategy
When dealing with large volumes of data,always use Bulk API	Define the use cases and the strategy early in the process
Best Practices 1) Sequence of Load is important 2) Sort the data by parent ID to reduce locking 3) Clean the data outside Salesforce before Loading (ETL Tools) 4) Disable unnecessary triggers, validation rules, workflows 5) Use efficient batch sizes	Best Practices 1) Full Copy Sandbox Recommended 2) Keep the data volume and data profile similar to Production 3) Consider UI, Integration and Data Loading Use cases for performance. 4) For integration, mimic the number of virtual users to be at least 50% of production.

How do we define scale?

Data Model for Scale