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

Devising a strategy for data backup

A key item to determine as part of a backup strategy is to have a rough idea of how much it's going to cost if access to some or all of the data was lost, and the cost of replacing that data if it is lost permanently. This is where the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are important. The RPO defines the amount of data you can lose before a successful restore happens, whereas the RTO defines the amount of time a business can be without access to the data. The first one is a key driver in determining how frequently the backup should be running and the RTO is a key consideration for how much downtime you can afford when you don't have access to your data. It is important to note that the RTO and RPO mentioned here refer to the portion of the data and metadata that the customer is responsible for. Disasters that happen in the infrastructure for which Salesforce is responsible have very efficient RPOs and RTOs...