Skip to main content

Flow Based Programming (FBP)

I have been a fan of FBP since I watched the first kickstarter video for noflo. Forget the metrics associated with CSV imports I saw a much bigger solution for a very real problem. My only objection was that noflo was implemented in javascript/coffeescript and while not unfamiliar was not going to take me where I needed to go which was writing complex server applications in addition to UX. I was finally able to implement a Flow based framework in golang which is now the basis for a number of applications including a reporting DSL, payment gateway transactions, and a few webapps.

While I was doing some reading for a client I found myself reviewing Meteor thinking that it might be a good framework for them... which then triggered my noflow memories. I went back to noflo and flowhub only to discover that they are not making much progress. The changelog suggests that they are in maintenance mode. I'm pretty sure that while FlowHub was supposed to be a PAAS (similar to Meteor's Galaxy) it turned into some other sort of platform which looked more like shopify than a hosted FBP. Furthermore the noflow commit log is also pretty slow.

Flow Based Programming rocks! In my experiments I have been able to implement the "steps" much the way someone might implement regular methods, however, having a framework to stitch it all together means that error trapping, metrics, reuse can be global.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…