| The documentation is scattered, but the best information can be found at: https://github.com/cocaine/cocaine-docs-en/wiki https://github.com/cocaine/cocaine-core#readme https://github.com/cocaine/cocaine-core/wiki The docs state that they refer to the 0.9 version, while development is going on in the 0.11 branch, so the docs might be more of less out of date. It seems that they have already implemented a large part of the Heroku infrastructure, including service discovery, auto balancing, cross-language events (using ZeroMQ) and that they are using it in production. All in all, an impressive feat! It would be interesting to hear if anyone has experience running/using this outside of Yandex. The source code seems well written, though comments are quite sparse. As Lazare remarked, it seems to directly compete with flynn.io. It is good to see that different high-level platforms are created based on docker. But it would be nice if these platforms would consist of modules (for example service discovery or messaging) that can be used without using the whole kitchen-sink. I am not sure if this is possible with cocaine. BTW, the repo cocaine-core is quite a bit older (since 2011) than docker (since early 2013?). The docker-core readme states that docker support is "on it's way" so it is not clear how mature this is. P.S. As adults and hackers, can we look beyond the name at the technology presented here? |
- They released the Docker plugin shortly before the conference [1] - Yandex uses a distributed storage system called Elliptics [2] in many places, and they implemented an Elliptics backend for the Docker registry (the code is out there somewhere. They contributed the Elliptics backend to the Docker registry repo a couple of days ago [3]. - Cocaine is used to power various things inside Yandex, like the Yandex.Browser backend. This backend can sustain very high loads (10-100k req/s). I discussed with their Ops team, since they had specific questions about how to identify (and remove) potential performance bottlenecks in Docker networking stack. (Good news: you can achieve native network performance within containers with zero overhead!)
I'm considering writing Dockerfiles for Elliptics and Cocaine (as soon as I can find some spare time to do so...) but I would also be happy to help if other people want to do that (I'm actively monitoring the docker-user mailing list [4] so don't hesitate to get in touch through here).
[1] https://github.com/cocaine/cocaine-plugins/tree/master/docke... [2] https://github.com/reverbrain/elliptics [3] https://github.com/dotcloud/docker-registry/pull/101 [4] https://groups.google.com/forum/#!forum/docker-user