Sam Goodwin
Sam describes a cloud application as a computation: a description of work with a result or error. Its infrastructure context is the cloud environment and dependencies in which it runs. Its flow is the sequence of work. Happy Path 116, 24:55.¶
He explains that runtime clients, business logic, and infrastructure policies stay related even when they live in separate files. Happy Path 116, 30:31.¶
He built cafe, the reference app for the CAFE stack16.¶
Sources
- #116 Infrastructure as Effects with Sam Goodwin - YouTube. Sam Goodwin. Infrastructure conversation; used for Sam's Effect and Alchemy explanation. Accessed 2026-10-01.
- Alchemy, Infrastructure as Effects | Office Hours 27 🔥 - YouTube. Sam Goodwin. Office-hours demonstration; used for infrastructure as Effects. Accessed 2026-10-01.
- Sam Goodwin - Alchemy - YouTube. Sam Goodwin. Alchemy interview; used for Layers, cloud libraries, and SaaS as NPM. Accessed 2026-10-01.
Last changed 2026-10-09 in 42ab7e2. Source on GitHub. Change log.
Linked from
- Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
Sam Goodwin — Sam Goodwin presents Alchemy as infrastructure built from Effect programs and typed requirements.
- CAFE names the Cloudflare, Alchemy, Foldkit and Effect stack. CAFE is a named stack: Cloudflare runs the app, Alchemy declares it, Foldkit draws the UI, and Effect does the typed work.
Sam Goodwin, who wrote Alchemy, built it.
- Change log. What changed in the files served here, newest first.
Sam Goodwin — edited: docs(lore): add CAFE stack page
- Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
- learn-alchemy. Learn how Alchemy 2 turns an Effect program into a planned Cloudflare deployment.
Sam Goodwin describes an Effect as a promise with more information: its return value, errors, and requirements.
- Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.
Sam Goodwin — Sam Goodwin presents Alchemy as infrastructure built from Effect programs and typed requirements.
- Source change history (log.md). The generated change log as Markdown.
Sam Goodwin — edited: docs(lore): add CAFE stack page