Flow-Based Programming
Flow-Based Programming (FBP) originated at IBM Canada in the early 1970s and was formalized by J. Paul Morrison in his 1994 book 'Flow-Based Programming,' modeling apps as networks of black-box components exchanging data via bounded-buffer connections rather than shared state. NoFlo, the best-known JS implementation (MIT license, ~3.5k GitHub stars), sat at v1.3.0 for roughly five and a half years before a maintenance push shipped v1.4.0-v1.4.3 (Dec 2020) and then v1.5.0-v1.5.2 (Jun 2026, the current release, with commits as recent as Jul 2026); it remains community-maintained after Flowhub UG's 2016 acquisition of creator Henri Bergius's project. Flowhub's own visual IDE (github.com/flowhub) has been largely dormant since its last real commits in early 2023. Node-RED, IBM-originated and now stewarded by the OpenJS Foundation (Apache-2.0), shipped v5.0.1 on July 1, 2026, and is the most actively developed FBP-adjacent tool. Newer entrant Flyde (MIT core, AGPLv3 editor) sat at ~3.5k stars as of May 2026. Current version/status: Concept is versionless (est. 1970s IBM, formalized 1994); leading implementations: NoFlo v1.5.2 (Jun 2026, after a ~5.5-year gap since v1.3.0/Nov 2020), Node-RED v5.0.1 (Jul 2026, active). License: Varies by implementation: NoFlo and JavaFBP are MIT; Node-RED is Apache-2.0; Flyde is MIT (core) + AGPLv3 (visual editor). Maintained by No single maintainer f
Pick classical FBP (JavaFBP/DrawFBP, or NoFlo for JS shops) when you need long-running, testable component networks with explicit backpressure and want to swap pieces without touching the rest - ETL and hardware-integration pipelines are the sweet spot. Skip it for anything needing continuous, mission-critical maintenance cadence: NoFlo went quiet for about five and a half years after v1.3.0 (Nov 2020) before a Jun 2026 burst of releases (v1.5.0-v1.5.2) - real, recent activity, but a long dormant stretch behind it - and Flowhub's IDE has been dormant since 2023, so reach for Node-RED (still shipping, v5.0 in June 2026, OpenJS-backed) or Flyde if you want visual dataflow with a pulse. Morrison's own site admits NoFlo and its peers are 'FBP-inspired,' not true FBP - no back pressure, no IP lifetimes, single-threaded. That's the tell: most 'FBP' tools people reach for aren't the real thing. Known weakness: Morrison's own comparison page concedes that NoFlo and its peers are only 'FBP-inspired' - they run single-threaded on Node.js and lack true asynchronism, information-packet lifetimes, and back pressure, so they can't handle the large data volumes classical multi-core FBP (JavaFBP/C