Building low-overhead metrics collection for high-performance systems
blog.wallaroolabs.com
blog.wallaroolabs.com
We have a few clients who will be running Wallaroo in production in the upcoming months. We're still a fairly new product, hoping to have one of those stories out in the not so distant future.
Is there anything you'd like to gain from one of those stories? Would be helpful to us to have a target audience in mind.
What we did do from scratch was write the instrumenting of Wallaroo in order to collect the metrics that could be used by our Metrics UI or Prometheus.
We thought it'd create a better user experience to provide a tool that provides the metrics information in a meaningful way as opposed to letting our users pick from Prometheus, Grafana, etc off the bat and having them set it up themselves.
In the end, if a user wants to use a tool like Prometheus they can write an adapter to convert our Metrics Protocol into a format suitable for Prometheus.
Yes. The core of Wallaroo is for high-throughput, low-latency stream processing.
We currently have a Python 2.7 API released and Go API preview release out.
I don't think of it as a competitor to Kafka although Kafka streams does provide a means to do stream processing.
There's a number of JVM based solutions out there (Apache has several). We are looking to be the solution for folks who want to use Python, JavaScript, Go and other non-JVM languages.
At this time, we support Python 2.7 and Go (preview release is out).
Python 3 and JavaScript are on our roadmap.
Java/C# would be things we'll be considering for the future.