Functional core
A functional core is an architectural component that performs domain computations through explicit inputs and outputs with minimal side effects.
Unit Testing Principles, Practices, and Patterns
A functional core is the part of an architecture that makes decisions through computations with explicit inputs and outputs and minimal side effects.
- How it is used
- Separates business decisions from side effects to improve maintainability and enable output-based testing.
- How deep it goes
- Explains explicit values, mutable shells, refactoring steps, testing boundaries, and performance and code-size trade-offs.
- Examples
- Uses discount and increment functions, an audit-file system, FileContent and FileUpdate values, Persister, and ApplicationService.
- What you can do after
- Build it from scratch by moving decisions into pure computations, returning explicit updates, and leaving external effects to a thin shell.
Read how Unit Testing Principles, Practices, and Patterns explains functional core →
Data-Oriented Programming in Java
The deterministic core is the central part of an application containing domain logic whose results do not depend on side effects or nondeterministic interactions.
- How it is used
- Organizes domain logic around determinism and isolates it from side effects, service calls, and environmental inputs.
- How deep it goes
- Explains dependency boundaries, code placement, and input-output testing, but stops short of prescribing one package or class structure.
- Examples
- Uses late-fee processing, past-due invoices, CSV deserialization, generated account states, and value-based assertions.
- What you can do after
- Apply via pure functions and input-output tests that transform, generate, and compare domain data without configuring external dependencies.
Read how Data-Oriented Programming in Java explains functional core →
Acing the Frontend Interview
A functional core is an architecture component that performs domain transformations through pure, composable functions without side effects.
- How it is used
- Separates predictable domain transformations from stateful interactions with external systems.
- How deep it goes
- Explains purity, composition, adapters, and pipeline flow through a worked data-processing example.
- Examples
- Uses filtering, mapping, reducing, summarization, pipe(), DataSource, and DataSink in one processing pipeline.
- What you can do after
- Build a testable functional pipeline that integrates API-fetching and result-saving modules.
Read how Acing the Frontend Interview explains functional core →
What to know first
- side effectA side effect is an observable change or interaction caused by a computation beyond producing its direct result, such as modifying state or interacting with the external environment.
- pipelineA pipeline is an ordered sequence of connected processing stages through which data or work flows, with each stage passing or transforming its output for subsequent stages.
Related concepts
- functional programmingpart of · Functional programming is a programming paradigm that expresses computation through the evaluation and composition of functions, typically favoring immutable data and minimizing mutable state and side effects.
- imperative shellcontrasts with · An imperative shell is a boundary component that performs side effects and handles interaction with external dependencies around a functional core.
- mutable shellcontrasts with · A mutable shell is the architectural part that handles state changes, side effects, and communication with external systems around a functional core.
- nondeterminismcontrasts with · Nondeterminism is the property of a system or computation in which the same inputs and conditions can produce different possible behaviors or outcomes.
- dependency directionconfigured by · Dependency direction is a constraint specifying which software components or architectural layers may depend on one another.
- pipelinepart of · A pipeline is an ordered sequence of connected processing stages through which data or work flows, with each stage passing or transforming its output for subsequent stages.
Questions about functional core
What is functional core?
A functional core is an architectural component that performs domain computations through explicit inputs and outputs with minimal side effects.
Which Manning books explain functional core?
Unit Testing Principles, Practices, and Patterns, Data-Oriented Programming in Java and Acing the Frontend Interview.
What should I know before learning functional core?
Manning books that teach functional core usually introduce side effect and pipeline first.
What is the difference between functional core and imperative shell?
A functional core is an architectural component that performs domain computations through explicit inputs and outputs with minimal side effects. An imperative shell is a boundary component that performs side effects and handles interaction with external dependencies around a functional core.
What is functional core part of?
Functional core is part of functional programming. Functional programming is a programming paradigm that expresses computation through the evaluation and composition of functions, typically favoring immutable data and minimizing mutable state and side effects.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


