This was originally “Yahoo! Traffic Server”, was developed by Yahoo! in the early 2000’s and was used in part to power Yahoo! CDN. At the time Yahoo! relied on Akamai and its own network.

It was developed by inktomi[1]; inktomi was acquired by yahoo in the one of the great extinction events of the early internet.

[1]https://en.wikipedia.org/wiki/Inktomi

Is it possible to abstract the metadata store, which is currently Zookeeper, to be something else like etcd and consul?

Since Mesos uses Zookeeper and we are tightly bound to Mesos, at the moment this is not possible.

To expand on this. We use mesos. Mesos is mostly deployed with zookeeper. 'Technically' we can by swapping the library, but unlikely.

Thanks. Wasn't sure you were using the Zookeeper instance used by Mesos. I had assumed it would be a separate instance.

I really like the idea behind Concord. No longer have to stress about Hadoop/YARN platform, and I can use the language of my choice (haven't used JVM-based stack in ages).

Is there documentation on adding more input/output sources?

If by 'input/output' sources, you mean computations that will pull or push from an external system such as kafka/cassandra, there isn't any documentation currently. However we have written connectors to Kafka and Kinesis. You can check out the Scala Kafka Source here [1]. Internally we are working on a high performance Kafka Source in C++ (based on librdkafka). At the moment this source can push records downstream at a rate of > 350K QPS.

[1]: https://github.com/concord/concord-jvm/tree/master/concord_k...

I meant connectors. Thanks for the pointer.

Concord's FAQ has a section on getting data into the system [1]. An example I've used is processing xml files at scale. A short input function digests the xml stream from our servers and another short output function creates a new document in Elastic.

[1] http://concord.io/docs/faq.html#how-do-i-get-data-into-the-s...

http://concord.io/docs/faq.html

This is definitely a big step forward. I had become spoiled by Go's cross compile capabilities, which Rust had paled in comparison to. Prior to this, it was a pain having to get the right toolchain for each platform. With this, I can download the toolchain as needed for the target platform, and build against it.

Aerospike maintains a comprehensive set of tests for the server. Every commit goes through functional and regression tests. Each release goes through a gauntlet of performance and clustering tests. The test system is a standalone system from the database, and is integrated with our CI system. Unfortunately, we have not been able to publish our test system, yet.