Book Image

Salesforce B2C Solution Architect's Handbook

By : Mike King
Book Image

Salesforce B2C Solution Architect's Handbook

By: Mike King

Overview of this book

There’s a huge demand on the market for Salesforce professionals who can create a single view of the customer across the Salesforce Customer 360 platform and leverage data into actionable insights. With Salesforce B2C Solution Architect's Handbook, you’ll gain a deeper understanding of the integration options and products that help you deliver value for organizations. While this book will help you prepare for the B2C Solution Architect exam, its true value lies in setting you up for success afterwards. The first few chapters will help you develop a solid understanding of the capabilities of each component in the Customer 360 ecosystem, their data models, and governance. As you progress, you'll explore the role of a B2C solution architect in planning critical requirements and implementation sequences to avoid costly reworks and unnecessary delays. You’ll learn about the available options for integrating products with the Salesforce ecosystem and demonstrate best practices for data modeling across Salesforce products and beyond. Once you’ve mastered the core knowledge, you'll also learn about tools, techniques, and certification scenarios in preparation for the B2C Solution Architect exam. By the end of this book, you’ll have the skills to design scalable, secure, and future-proof solutions supporting critical business demands.
Table of Contents (20 chapters)
1
Section 1 Customer 360 Component Products
7
Section 2 Architecture of Customer 360 Solutions
13
Section 3 Salesforce-Certified B2C Solution Architect

The Packt Gear approach

To recap our solution so far for Packt Gear, we've decided they need Service Cloud, Order Management, B2C Commerce, and Marketing Cloud to form their basic B2C solution architecture.

Based on the information learned in this chapter, we'll need to decide whether they should be leveraging the point-to-point integration approach, integration middleware, or a single source of truth architecture.

Let's start by reviewing the key reasons why adding an integration middleware solution such as MuleSoft would be the right choice for a solution:

  • MuleSoft is already being used in the client ecosystem.
  • There are plans for multiple integration points beyond the core three Salesforce platforms.
  • Point-to-point connector integration patterns are not appropriate for the specific customer scenario and a more complex integration is required.
  • There's a strong preference for minimizing product customization and keeping integration in...