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

Learning data management best practices

In this section, we will be learning data management best practices within the context of Salesforce. You probably already realize that Salesforce is increasingly being used for more than just CRM, and companies are using it for critical business functions. Even if it was only used as a CRM, data would be very important and require continuous data management.

In my opinion, gone are the days when you could go to your production org and add or modify existing functionality because a user requested it. With more intra-dependencies between applications built on the platform and inter-dependencies between external systems and Salesforce, changes concerning data and metadata, in particular, must be thought through. I am not proposing spending hours and days analyzing what impact adding a new list view is going to have, but pragmatically approaching changes to your production environment based on the size of the change and how interlinked it is...