Welcome to the GO-LIVE series, a set of articles about preparing for the launch of one or more channels on Salesforce B2C Commerce Cloud.
This is only the second article so far, but after releasing the first one about the eCDN, I felt I might have skipped some vital information.
Sure, there was an explanation of the eCDN and its use. But not how it fits in the “bigger picture.” So let us look at the architecture of the different environments in Salesforce B2C Commerce Cloud!
Before we move into the details where the Embedded CDN (eCDN) is mentioned, let us get an overview of the components that make up “SFCC.”
Commerce Cloud Core
We can’t forget about one of the big selling points of SFCC, the “built-in” AI that will analyze shopper behavior and give recommendations to increase revenue and the average size of the basket.
Note: I have an article explaining what Einstein is and what it can do in the pipeline!
As you can see in the diagram at the top of the section, the SCAPI is a set of RESTful APIs built in MuleSoft that proxy the OCAPI behind the scenes to allow some extra things on top of the original OCAPI.
But besides having some APIs that the OCAPI does not have, there are some drawbacks (for now).
Can’t find your way in the logs on the WebDAV? Have no fear; Log Center is here.
In the Log Center, you can easily filter and search for specific log entries and even be notified when particular thresholds are met.
Reports & Dashboards
Need insights on your sales or site performance? In this tool, you can view statistics on:
- Technical data (performance)
The place to be if you want to manage all of your environments (Sandboxes, PIG Instances). Using this tool, you can create, start, restart, stop and reset environments linked to your account.
The latest addition to the diagram, the answer to all your Headless Storefront needs!
Since all of the items mentioned above are separate tools/sites you have to visit, it would be a shame if you had to keep track of different credentials (you had to for a long time).
Account Manager provides you with “Unified Authentication” so that permissions and user credentials can be managed from a central location, rather than having separate ones for each application.
From the perspective of a request
In the diagram below, we look at a potential request to an SFRA or SiteGenesis channel and see what different layers it passes before a visitor gets a page rendered in their browser!
In this case, the explanation of each component of the environment is in the diagram itself. Word of warning though, this is a lot more “technical” than the previous section.
Layering the CDN
It is possible to introduce your CDN (e.g., Akamai) or your own Cloudflare account next to the eCDN.
The critical thing to remember is that the eCDN will always be part of the chain!
As of August 2022, Origin Shielding has become active. All storefront (shopper) traffic must pass through the eCDN (Cloudflare).
This change does not affect:
- Business Manager
- Inventory Service
- Analytics Service
- Mainstreet Order Management Service
- Order Integration Service
- Salesforce Commerce API (SCAPI) calls
- Shopper Login (SLAS)
- Image Downloader Service
- WebDAV calls
- /dw/monitor calls for health checks
- sffc-ci tool (developer instance only)
- Data APIs