Skip to main content

Introduction

You already know what version control is. You've probably used Git. You may have built a CI/CD pipeline or two. You understand deployments, environments, and test execution.

And yet, if you've worked on Salesforce DevOps for any length of time, you've run into the same wall: the tools that work reliably everywhere else don't behave the same way here. Merges succeed and deployments break. Pipelines pass in staging and fail in production. Rollback is a word that has no real implementation. Drift appears from nowhere and compounds silently.

This course is a first-principles investigation of why that is.

What you'll walk away with​

By the end of this course, you'll be able to:

  • Articulate the architectural properties of Salesforce that make standard DevOps tooling insufficient, not as a list of edge cases but as a coherent structural argument
  • Name and explain all seven ways standard practices fail against Salesforce's architecture, with the technical mechanism behind each
  • Evaluate any DevOps tooling claim against a defined set of architectural requirements
  • Make the engineering case for a metadata-native approach to a technical audience

This course intentionally stops short of prescribing specific tool configurations or workflows. The goal is architectural understanding: the kind that lets you recognize when a solution addresses the root cause versus patches a symptom.

How to use this course​

Six Lessons, eight to ten hours of material, structured for working engineers. You can read linearly or jump to sections using the Lesson index. Lesson 3 (The Seven Mismatches) is the technical core. Everything before it builds the conceptual frame; everything after it quantifies the consequences and examines the solution space.

The certification assessment at the end is scenario-based: it asks you to apply the architectural reasoning from this course, not just recall definitions.

Where this fits in the curriculum​

This is the foundations Lesson of the Flosum certification curriculum, the shared starting point for both the business and engineering tracks. The concepts introduced here are prerequisites for all subsequent courses in the curriculum.