liveBook · Manning

Functional core

As explained in Acing the Frontend Interview

A functional core is an architecture component that performs domain transformations through pure, composable functions without side effects.

A functional core handles domain transformations with pure, composable functions. It accepts inputs, returns outputs, avoids mutation and external state, and remains predictable and testable. section 3.2

Separate transformation logic from stateful integration work:

  • Place API calls, database queries, file operations, and external-system writes in an object-oriented shell or adapter. section 3.2
  • Compose transformations with pipe() or compose() to create a modular, declarative data flow. section 3.2

Interview-ready pipeline

A DataSource fetches raw records, the core filters valid items, doubles their values, and summarizes count and sum, then a DataSink saves the result. This separation supports isolated testing and easier extension.

How Acing the Frontend Interview covers it

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 it assumes
Assumes JavaScript or TypeScript fundamentals while practicing pure functions, map, filter, reduce, and immutability.
What you can do after
Build a testable functional pipeline that integrates API-fetching and result-saving modules.
How it connects
Connects pure functions, immutability, higher-order functions, currying, pipelines, adapters, and object-oriented modules.

Also explained in

Compare how 3 books explain functional core →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.