og.rsts.dev

Series

Dreamforce 2026

Architecture-first dispatches from Salesforce Dreamforce 2026: Data 360 as the grounding layer, the on-platform versus off-platform agent decision, MuleSoft Agent Fabric, native source-driven DevOps, and where Azure AI Foundry interop is real versus marketed.

4 parts · 50 min total · Sep 2026

A short series written in and around Salesforce Dreamforce 2026. Architecture-first reads on Data 360, Agentforce, MuleSoft Agent Fabric, native DevOps, and the question every architect walks into the keynote already asking: where are the boundaries, and which of them will the vendor happily blur to sell me the same capability twice?

  1. Part 01 12 min Draw the Boundary Before You Buy Deeper I'm flying out early for the Data 360 developer bootcamp, but the bootcamp is the cheap part. The hard question at Dreamforce is where the boundaries are: on platform versus off, data versus integration versus action, and whether source-driven development is enforced or just available. Here are the questions I refuse to leave without answering.
  2. Part 02 10 min Data 360 Is a Reference System, Not a Database What the Data 360 developer bootcamp actually taught me: its real power is as a semantic layer over data you never move, a reference system rather than another place to manage records. Two places that reframe pays off: marketing segmentation, and unifying one person's fragmented logins across every portal a bank runs.
  3. Part 03 12 min The Model Decides, the Code Controls The post-Dreamforce answers to the three questions every regulated shop is asking about agents: where the model decides and where the code does, why shipping is the real work and not the demo, and how bounded economics give a CFO a number to underwrite. The governance is what gets agents into production, not what holds them back.
  4. Part 04 16 min AI Replaces the UI. What an Architect Actually Takes Home Dreamforce 2026's headline was AIforce: AI replacing the interface itself. Underneath it sits an old argument with two right answers. The customer and the banker want the friction gone. The architect has to keep control of identity, data, and cost. Here is the honest case for each side, grounded in what the keynotes actually said, and how the control plane lets you say yes to both.
Start with Part 1 →