https://blog.kodigy.com/tags/noflo/ Recent content in noflo on A system brought to life Hugo -- gohugo.io en-us © Vladimir Sibirov. Code released under the MIT license. Mon, 13 Mar 2017 18:25:04 +0300 https://blog.kodigy.com/post/noflo_08_npm_shrinkwrap/ Mon, 13 Mar 2017 18:25:04 +0300 https://blog.kodigy.com/post/noflo_08_npm_shrinkwrap/ Using NPM Shrinkwrap to force NoFlo 0.8 Recently released 0.8 branch of NoFlo introduces several fundamental changes as well as a backwards compatibility layer for long-existing applications. However, the backwards compatibility layer is only capable of doing its job if all NPM dependencies in a project use noflo@0.8.*. Which means that if a project uses an old library that depends on something like noflo@0.5.22, the compatibility layer may work incorrectly. https://blog.kodigy.com/post/noflo_development_efficiency/ Mon, 07 Nov 2016 17:39:26 +0100 https://blog.kodigy.com/post/noflo_development_efficiency/ Development efficiency challenges in NoFlo Programming with NoFlo is getting more and more smooth with every release. However, if maintaining a NoFlo application is your day-to-day job you may notice some inconveniences. Defining new components is slow Every time you add a new component you have to define a pretty massive hash map of its ports, their data types and preferably at least descriptions. This is cool as it encourages you to declare as many details as possible but it’s not very friendly to rapid prototyping where you want just to list the ports and get your hands on the code and add details later. https://blog.kodigy.com/post/on_noflo_db_apps/ Wed, 27 Jul 2016 14:25:04 +0100 https://blog.kodigy.com/post/on_noflo_db_apps/ On NoFlo Database Applications Thinking over common parts of database applications… … I came to some conclusions below Common application architecture Steps common to all route graphs The only processing step that is often present and easy to decompose is Validate (fig. I and II). String of pearls or Pipeline or Request backbone Request flow should be serial, it simplifies synchronization and understanding of the flow. Each bone in the spine of the graph or step on the pipeline can process some data in parallel. https://blog.kodigy.com/post/noflo_webservices/ Fri, 23 Jan 2015 14:38:41 +0100 https://blog.kodigy.com/post/noflo_webservices/ Getting All Things NoFlo This article describes things which are yet TODO to get the entire server architecture running on NoFlo (and in Flowhub), problems related to them and potential solutions. Request Isolation By default there is no isolation between IPs belonging to different user requests in NoFlo networks. Solution 1 (current): a new Network instance per request Express does its job conventionally, while request handlers instantiate NoFlo networks on demand.