Erlang has been my latest hobby language, and while I'm not very deep into it yet I'm having fun looking through the source code here to see what "real Erlang" looks like.<p><a href="https://github.com/basho/riak_cs" rel="nofollow">https://github.com/basho/riak_cs</a><p>If any experts happen to notice particularly good or heinous examples in this source code, it'd be interesting to point them out.
We've been pretty happy users of Ceph for months now, but it's great to now have a second S3-compatible solution for distributed storage.<p><a href="http://ceph.com/" rel="nofollow">http://ceph.com/</a>
Mildly-shameless plug here: Riak CS will a big topic at RICON EAST this May in New York City (in addition to Riak and other distributed systems goodness). You should all attend.<p>- Conf info: ricon.io/east.html
- Tickets: <a href="http://ricon-east-2013.eventbrite.com/" rel="nofollow">http://ricon-east-2013.eventbrite.com/</a>
This is excellent news. Questions though...does Riak CS need its own dedicated Riak cluster or can you use "its" Riak nodes directly in the usual Riak fashion? If so, is it possible to access the CS-created chunks directly? (Not saying that is a good idea...just trying to understand how Riak and Riak CS fit together.)
+1 on the excellent news, makes it especially easy for hobbyist like myself to mess around with this sort of thing.<p>Awesome to see use of vagrant to get started quickly!