Salesforce Winter '27 for Agentforce and Data 360: What Actually Changes
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Integration Architect
Integration architecture: turning a business need into requirements, designing the solution, and keeping it alive past year two.
Designed and created by Salesforce Expert
What you'll learn
- Read an inherited landscape and find the business need under it
- Turn that need into integration requirements you can design against
- Choose patterns and technologies for the requirement, not the fashion
- Design for operability: monitoring, retries, and the second year
- Defend a complete integration design end to end
Course content
7 sections · 38 lectures
What this exam asks, and what it does not 3 lectures
- 1.1 Sixty-seven per cent
- 1.2 Three domains are three-quarters of the paper
- 1.3 "Given a use case"
The landscape you inherit, and the business need underneath it 6 lectures
- 2.1 Nobody hands you a landscape
- 2.2 Standards, limitations, boundaries and protocols
- 2.3 A constraint, a pain-point and a preference are three different objects
- 2.4 Reading the authentication and authorization needs off the landscape
- 2.5 Non-functional requirements decide the design
- 2.6 Confidential, Secure, Public
Translating a business need into integration requirements 7 lectures
- 3.1 From a landscape diagram to an inventory of interfaces you can count
- 3.2 Naming the pattern of every interface you found
- 3.3 System constraints and process constraints fail differently
- 3.4 Volume, response time and latency — turning "it should be fast" into a number
- 3.5 Peak is the requirement. Average is a comfort
- 3.6 Integration security requirements: what must be true before a byte moves
- 3.7 The requirements artefact an integration architect actually hands over
Designing the solution 9 lectures
- 4.1 The integration patterns, and the four questions that pick one
- 4.2 Synchronous or asynchronous is a business decision wearing a technical hat
- 4.3 Choosing an API when the exam guide names none
- 4.4 Salesforce as the provider, Salesforce as the consumer
- 4.5 Middleware: when point-to-point is right, and when it has quietly become twelve of them
- 4.6 Copy it, reference it, or leave it
- 4.7 Defining the components of a solution
- 4.8 Trade-offs, limitations and constraints, said out loud before anybody asks
- 4.9 The security mechanism for the interface
Building it so it survives its second year 7 lectures
- 5.1 Designing an inbound API you will still be able to change in three years
- 5.2 Making the outbound call: the options, and the question that chooses between them
- 5.3 Scalability is a shape, not a number
- 5.4 Error handling: what you retry, what you park, and what you must never retry
- 5.5 Idempotency, ordering, and the duplicate you are definitely going to create
- 5.6 A security solution for one interface, inbound and outbound, end to end
- 5.7 Resilience across system updates
Keeping it alive 3 lectures
- 6.1 Monitoring an integration you can only see one end of
- 6.2 Escalation and recovery after it has already failed
- 6.3 Reporting for integration monitoring
Merrivale, end to end 3 lectures
- 7.1 The use case as an exam would hand it to you
- 7.2 A worked solution, interface by interface
- 7.3 The other design that would also have passed
Requirements
- BLD-110 Apex Foundations or equivalent programmatic literacy
- Experience of at least one real integration
Description
This course separates what the Integration Architect exam asks from what it does not, then works the real sequence: the landscape you inherit and the business need underneath it, translating that need into integration requirements, designing the solution, building it so it survives its second year, and keeping it alive.
Merrivale — a worked scenario — is then taken end to end. It covers the Platform Integration Architect blueprint.
Who this course is for
- Architects and senior developers designing integrations between Salesforce and everything else.
Skills you'll practise
Related reading
Grounding Agentforce in Data 360: Structured Data, Intelligent Context and the Latency Trap
Four ways to ground an agent in Data 360, when each is right, and why zero-copy federation is the wrong choice for the retrieval path of a live conversation.
Agent Script vs Subagents and Actions: When to Make an Agentforce Agent Deterministic
Every Agentforce project has this argument in week three. The rule that sorts deterministic steps from generative ones, and why each half needs a different test.