functional-core-imperative-shell

To improve code maintainability, you implement the Functional Core, Imperative Shell pattern to separate business logic from side effects, encapsulating core operations in pure functions and isolating I/O operations in an imperative shell.

The functional core imperative shell pattern is a software architecture approach that separates deterministic business logic into pure functions and handles I/O operations through an imperative shell to enhance codebase testability and maintainability.

You refactor existing code by following the FCIS pattern guidelines, extracting core business logic into pure functions to ensure deterministic results, and moving I/O operations into a separate imperative shell for easier error handling and code reuse.

You should use the functional core imperative shell pattern when refactoring codebases that suffer from tightly coupled business logic and I/O operations, aiming to enforce separation of side effects and enhance overall testability and code reuse.

Separating pure logic from I/O operations makes testing easier by encapsulating core business logic in pure functions that produce deterministic results, allowing you to test the functional core independently of the imperative shell's side effects.

The limitations of the functional core imperative shell pattern include the overhead of refactoring tightly coupled legacy code and the architectural discipline required to consistently prevent I/O operations from leaking into the pure functional core.