"Currently, Apollo is developed internally at Facebook. No firm claims were made during the talk that it will be opensourced. It was mentioned as a possibility after internal development settles down." from <a href="http://java.dzone.com/articles/facebook-announces-apollo-qcon" rel="nofollow">http://java.dzone.com/articles/facebook-announces-apollo-qco...</a>
One of their supported storage primitives is CRDT-based, according to [1]. I, for one, am really interested to see how this works in practice. I've been quite excited about CRDTs, but haven't seen enough examples of them in the wild to get a sense of their drawbacks — for instance, how difficult it is to use them to model various processes or data structures.<p>[1] <a href="https://twitter.com/adrianco/status/476843040330743809" rel="nofollow">https://twitter.com/adrianco/status/476843040330743809</a>
> Apollo, Facebook’s Paxos-like NoSQL database ...<p>> supports anything from a minimum of three servers to thousands<p>Sorry, you don't run Paxos on thousands of servers. Typical Paxos cluster sizes are 5-7. The algorithm would never converge if you did run it on thousands of servers.
"is on-line low latency storage - in particular Flash and in-memory." "As distinct from a document oriented, or key value store, Apollo is about modifications to data structures, allowing you to represent maps, queues, trees and so on, as well as key values. "<p>Sounds like Redis?