The Eric Normand Podcast In the onion architecture, how do you make business decisions that rely on information from actions?
10 snips
Sep 16, 2019 Dive into the intriguing world of Onion Architecture! Discover how to make sound business decisions based on calculations rather than just actions. The discussion highlights the importance of structuring function calls effectively and separating responsibilities within software layers. Practical examples bring these concepts to life, making it clear how to navigate complex business scenarios with clarity and precision.
AI Snips
Chapters
Transcript
Episode notes
Name Decision Functions
- Name functions that encapsulate decisions, even simple ones like retry logic.
- This clarifies the separation between actions and calculations in Onion Architecture.
Layers as Function Calls
- Onion Architecture layers represent function calls, not communication protocols.
- Calculations call other calculations; actions call calculations and other actions.
Extract Calculations
- Turn inline decision logic within actions into named calculation functions.
- This clarifies business rules and simplifies actions.