Book Image

Salesforce Data Architecture and Management

By : Ahsan Zafar
Book Image

Salesforce Data Architecture and Management

By: Ahsan Zafar

Overview of this book

As Salesforce orgs mature over time, data management and integrations are becoming more challenging than ever. Salesforce Data Architecture and Management follows a hands-on approach to managing data and tracking the performance of your Salesforce org. You’ll start by understanding the role and skills required to become a successful data architect. The book focuses on data modeling concepts, how to apply them in Salesforce, and how they relate to objects and fields in Salesforce. You’ll learn the intricacies of managing data in Salesforce, starting from understanding why Salesforce has chosen to optimize for read rather than write operations. After developing a solid foundation, you’ll explore examples and best practices for managing your data. You’ll understand how to manage your master data and discover what the Golden Record is and why it is important for organizations. Next, you'll learn how to align your MDM and CRM strategy with a discussion on Salesforce’s Customer 360 and its key components. You’ll also cover data governance, its multiple facets, and how GDPR compliance can be achieved with Salesforce. Finally, you'll discover Large Data Volumes (LDVs) and best practices for migrating data using APIs. By the end of this book, you’ll be well-versed with data management, data backup, storage, and archiving in Salesforce.
Table of Contents (14 chapters)
Section 1: Data Architecture and Data Management Essentials
Section 2: Salesforce Data Governance and Master Data Management
Section 3: Large Data Volumes (LDVs) and Data Migrations

Conducting performance testing in Salesforce

The Salesforce Platform serves several billion transactions per day and is designed to be highly scalable. Given that Salesforce provides its platform as a service, they conduct extensive testing and monitoring to ensure that their platform can withstand the load that can be placed on the infrastructure.

Performance testing has two components:

  • Stress testing: Stress testing is used to measure system performance under extreme conditions using loads that are beyond the maximum expected load. The goal of stress testing is to determine the maximum limit the system can stretch to without crashing.
  • Load testing: Load testing, on the other hand, is measuring the performance of a system under expected loads. The goal here is to ensure that acceptable levels of service can be provided, or if there are formal SLAs, that they can be met.

An application that doesn’t perform well under heavy loads can crash the system and...