Before You Put an LLM in a Flow
Let an LLM generate content if the result is reviewable. Do not let it make the business decision.
Tag: architecture
8 posts in this channel.
Timeouts Need a Deadline, Not Just a Number
Giving every operation its own timeout can make one request take several times longer than intended. Pass the remaining deadline instead.
Trigger Architecture Without a 40-Class Framework
Most Apex trigger logic needs one entry point, thin routing, bulk-safe services, and change-aware guards. It does not automatically need a metadata-driven framework.
Props, Events, LMS, or State Manager?
LWC communication gets easier when the mechanism matches the relationship: properties down, events up, LMS across page boundaries, and state managers across a complex component subtree.
An Error Contract for LWC, Apex, and Flow
Errors become much easier to handle when LWC, Apex, and Flow agree on a small contract: stable codes for automation, safe messages for people, and correlation details for support.
Where Flow Should End and Apex Should Begin
Flow and Apex overlap, but they are not interchangeable. I use Flow for visible orchestration and Apex when data structures, transaction control, scale, or reuse become the real problem.
LDS vs GraphQL vs Apex: How I Choose an LWC Data Layer
LDS, GraphQL, and Apex can all put Salesforce data into an LWC. The useful question is not which one is best, but which is the smallest honest fit for the operation.
State Managers for LWC: Be Excited, Keep Your Components Raw
Summer '26 gives LWC a native state layer. Use it to coordinate complex pages without coupling every reusable component to one state shape.