Copyright © 2026 Authors retain the copyright of this article. This article is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

@article{202996,
        author = {Aditya Powar and Rajesh Khandagale and Vishwajeet Kamat and Farhan Shaikh},
        title = {FluxEngine: A Graph-Driven Runtime Interpreter for Visual Backend Development},
        journal = {International Journal of Innovative Research in Technology},
        year = {2026},
        volume = {12},
        number = {12},
        pages = {8197-8203},
        issn = {2349-6002},
        url = {https://ijirt.org/article?manuscript=202996},
        abstract = {The growing adoption of low-code development platforms (LCDPs) has revealed a persistent gap between workflow automation tools—which model service integrations but not API semantics—and general-purpose backend frameworks, which demand conventional programming expertise [1, 2]. Existing LCDPs either generate static source code, coupling the visual model to a specific framework and introducing a synchronisation problem on every graph edit, or restrict expressiveness to fixed integration patterns unsuitable for custom business logic [3, 4]. We present FluxEngine, an open-source, self-hostable visual backend development environment that eliminates code generation in favour of a stateful, graph-driven runtime interpreter. Users compose directed acyclic graphs (DAGs) of typed functional nodes on an interactive canvas; the interpreter traverses these graphs at request-time, dynamically registers Express.js HTTP routes, and propagates a structured execution context between nodes via a dot-path expression resolver. A dual-mode telemetry system streams per-node observability data to the canvas over WebSocket in development mode and suppresses all instrumentation in production. Empirical evaluation on a commodity four-core server demonstrates a median per-node interpreter overhead of 3.1 ms and a sustained throughput of 820 req/s for a six-node authentication workflow, establishing runtime interpretation as a viable, low overhead alternative to code generation for visual backend tooling.},
        keywords = {low-code development; visual programming; graph execution; runtime interpreter; backend automation; node-based workflow; WebSocket telemetry},
        month = {May},
        }