Since v0.61.0, FlowG can run as a cluster of nodes sharing a single FoundationDB storage. Storing the data is the easy part: FoundationDB replicates it for us. But saving a pipeline is more than a write. Something must be compiled, started, reloaded or stopped, and not just on the node that received the API call. On every node.
FlowG v0.63.1 makes this work. Here's how.
Say welcome to Amazon AWS, Google Cloud and Microsoft Azure!
Logs tell you what happened. Metrics tell you how much, how often, and is it getting worse. Most infrastructures pay for both, twice, with two different agents reading the same lines.
Since FlowG v0.62.0, they can share the work: a pipeline is now able to count the records flowing through it, and expose those counters to Prometheus.
馃帀 FlowG v0.61.0 has been released, and with it one of the two big projects we announced on the road to 1.0: replication is now generally available.
It is powered by a brand new storage backend, built on top of FoundationDB.
馃帀 FlowG v0.59.0 has been released, and it includes (since v0.58.0) a dark mode for the frontend!
馃帀 FlowG v0.55.0 has been released, and with it a new shiny feature: VRL Log Splitting.
馃帀 FlowG v0.54.0 has been released, finalizing the MVP milestone of our roadmap.
馃帀 FlowG v0.45.0 has been released with partial support for the ElasticSearch API!