I am a big fan of Functional Programming and Modular JavaScript. This project's goal is to demonstrate the latest Functional Promise patterns, while taking you through a refactor of real world callback-based NodeJS/JavaScript.

It is an async & sync version of the Collection Pipeline pattern.

Your parameters/data represents the water, and functions form the riverbed.

Roughly speaking, my definition of pipeline is a sequential series of chained functions where arguments line up with return values (using Array methods, Promises, or similar). Key to my adaptaion is using named functions.

This ultimately results in your code reading like a step-by-step story.

Compare these 2 examples:

// ❌ Non-Functional River / Collection Pipeline Code ❌
const formatScores = scores => scores
  .map(x => x * 2.0)
  .map(x = x.toFixed(2))

// ✅ Functional River Code ✅
const formatScores = scores => scores
  .map(double)
  .map(formatNumber)

Let's look at a more complex example, with asynchronous requirements added in the mix...

See both Before and After examples below.

Note: This is intentionally reasonable callback code. Even if nested. Not trying a straw-man attack.

The technique I demonstrate hopefully illustrates the Functional River pattern:

• Higher level logic implemented with multiple smaller single-purpose functions, assembled to read like a story.
• Decoupled modules are easier to maintain & upgrade over time.
• Reduce bugs by relocating ad hoc logic. (e.g. one-off transformations, untested validation)
• Use same interface for both synchronous & asynchronous code. (promise.then(value => alert(value)))
• Prefer immutable, stateless code as essential building blocks.
• Less elaborate, modular code is naturally more reusable.
• Easier to move logic around - rebundle simple functions as needed to create new higher-order functions.
• Increased testability - eliminate hidden surface area.
• Substantially faster code readability - versus artisinal functions assembled with ad hoc code glue (a Big Ball of Mud).

Note: The Functional River Relies on ideas from Lisp to SmallTalk - adapted to a JavaScript world. Apologies to Promise Resistance Leader Brian Leroux. For alternative patterns please read my more detailed article demonstrating 4 JavaScript Composition Techniques (with Examples)

If you feel this subject has already been exhauted, please see my post Beating a dead horse?

1. Step 1: Break Up The Big Functions - read the code: PR #2: Flatten Functions
2. Step 2: DRYer Code - read the code: PR #3: DRYer Code
3. Step 3: Cleanup Code - read the code: PR #5: Post Cleanup

• Less ad hoc code results in:
  • More uniform code between different teams & developers,
  • Performance tooling & refactoring is an appreciably better experience,
  • More certainty about code correctness,
  • Higher code reuse.
• 100% Unit Testability
  • Unit tests uniquely prove you found, understand, AND resolved a given bug,
  • Faster bug resolution process,
• Flatter code hierarchy == less filler to remember
  • Re-organizing code is easier & less prone to bugs - with Pure-ish Functions

• Performance. I've run some micro-benchmarks - it's not awesome. However, 3 important things:
  1. It's not meaningfully slower in real world applications.
  2. If it is necessary, performance analysis & tuning is a much improved experience. Smaller functions make it easier to see where slow code lurks - especially if you profile unit tests.
  3. As more people adopt these patterns, things will improve. V8/Chrome has been impressively fast at optimizing for emerging patterns.
• Debugging can be more difficult. Though I have updated my dev tricks to debug this style of code, even without the confort of Bluebird's error handling. I'll add more sample scripts for this later.
• Something new to learn. Deal with it, you're a developer.
• If you have an existing project with lots of code, the unfortunate reality is: Refactors Suck.
• EventEmitter- & Stream-based code is not improved much, if at all, using this technique. Look into RxJS
  • Ongoing experiments include simple closures, extend Promise with EventEmitter, or using Bluebird's .bind to inject variable state into the Promise chain. (I know, "ugh side-effects, gross." PRs welcome.)

It's perhaps true that an overly-done flat & modular JS Project can feel more disorganized over time. New practices & approaches must be explored (from monorepos, to breaking up modules when-needed to meet org/dev/deployment needs).

Project and code discipline is just as important as it's always been. Also, the community is still developing consensus around Functional JS patterns, immutability and overall project organization.

When done right, one of Functional River's greatest strengths is the ability to relocate & rearrange modules with low risk. If this still feels risky, your modules are probably still too entangled (coupled).

• Steps
  1. Step 1: Break Up The Big Functions
  2. Step 2: DRYer Code
  3. Step 3: Cleanup Code
• Related Articles
  • Finding Promise Anti-patterns
  • What about Async, Await and Generators?
• Examples
  • HTTP Client Work Queue
  • Typed Errors
  • S3 File API w/ Express Middleware & Class wrapper

I highly recommend reading (or watching) every single link here.

• Tom Stuart's Purely Amazing Programming with Nothing
• Eric Elliot's Tour de force: The Two Pillars of JavaScript
• Ashley Williams Speaks The Modular Tructh in A Brief History of Modularity | JSConf EU 2017
• And Eric's Rise and Fall and Rise of Functional Programming (Composing Software) is damn good too ;)
• Martin Fowler expertly lays down the Ruby + Haskell pipeline in Collection Pipeline

1. README now more focused on the Functional River pattern.
   • Counter-examples are still included in ./src, just not featured on README.
2. There's an updated production-ready library Functional Promises which grew out of the feedback & research from this Project.