Platform Architecture, Orgs and Releases

Salesforce Platform FoundationsPlatform Architecture, Orgs and ReleasesHow Salesforce's multi-tenant, metadata-driven platform actually works, the kinds of orgs you'll build in, how editions, licenses and the three-releases-a-year cadence affect your code, and where Apex, Flow, LWC and the APIs fit.Beginner · about 60 minutesWhat you will learn

Explain multi-tenancy and the metadata-driven kernel, and why they lead to governor limits

Describe how custom objects and fields are stored conceptually in shared tables

Choose the right org type (sandbox, scratch org, Developer Edition, Trailhead Playground) for a task

Tell user licenses, permission set licenses and feature licenses apart, and know when to use the Salesforce Integration license

Explain the three-release cadence and how API versions pin code behaviour

Apply a 'clicks before code' decision framework and place Apex, Flow, LWC and the APIs on the platform layer cake

Contents

Multi-tenancy: one platform, many customers

The metadata-driven kernel

Where your org lives: instances, pods and Hyperforce

Org types: where you build, test and run

Editions and licenses

Releases and API versioning

A tour of Setup and the Object Manager

The platform layer cake: where Apex, Flow, LWC and the APIs live

"Clicks before code": a decision framework

Worked example: getting to know a new org

Salesforce Clouds: a map of this course

Best practices

Common pitfalls

Hands-on exercises

Key takeaways