<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Riak on Roads Less Taken</title><link>https://goran.krampe.se/categories/riak/</link><description>Recent content in Riak on Roads Less Taken</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 Jul 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://goran.krampe.se/categories/riak/index.xml" rel="self" type="application/rss+xml"/><item><title>RethinkDB - Yet Another NoSQL?</title><link>https://goran.krampe.se/2013/07/16/rethinkdb-yet-another-nosql/</link><pubDate>Tue, 16 Jul 2013 00:00:00 +0000</pubDate><guid>https://goran.krampe.se/2013/07/16/rethinkdb-yet-another-nosql/</guid><description>&lt;p>15-18 years ago my passion was in OODBs. As a Smalltalker &lt;a href="http://www.gemtalksystems.com" target="_blank" rel="noopener noreferrer">GemStone&lt;/a>
 was one of the most fascinating to work with, but as we all know OODBs never got really popular, despite their fantastic qualities. But the new NoSQL databases in many respects offer OODB-ish characteristics, although they of course also bring a whole new menu to the table.&lt;/p>
&lt;p>In my eternal quest for &amp;ldquo;database bliss&amp;rdquo; my next stop is &lt;a href="http://rethinkdb.com" target="_blank" rel="noopener noreferrer">RethinkDB&lt;/a>
, but let me tell you how I got here.&lt;/p></description></item><item><title>Oak</title><link>https://goran.krampe.se/2012/12/29/oak/</link><pubDate>Sat, 29 Dec 2012 00:00:00 +0000</pubDate><guid>https://goran.krampe.se/2012/12/29/oak/</guid><description>&lt;p>In a customer project right now I need to be able to work and evolve code fast, with a relatively complex model. And by &lt;em>fast&lt;/em> I mean that I want to cut away as much as possible of the efforts related to persistence. Generally this is what OODBs excel at.&lt;/p>
&lt;p>In the Squeak world we have &lt;a href="http://www.gemstone.com/products/gemstone" target="_blank" rel="noopener noreferrer">GemStone&lt;/a>
 (commercial), &lt;a href="http://wiki.squeak.org/squeak/3492" target="_blank" rel="noopener noreferrer">GOODS&lt;/a>
 and &lt;a href="http://wiki.squeak.org/squeak/2665" target="_blank" rel="noopener noreferrer">Magma&lt;/a>
 as &amp;ldquo;full fledged&amp;rdquo; OODBs. Last century :) I worked with GemStone (both Gemstone/S and /J) and its a great product - but I want something lightweight and open source. And simple. And hackable. And new. :)&lt;/p>
&lt;p>I also used Magma in the Gjallar project, and while I respect it highly - this time I want to try something with an &amp;ldquo;externally supported backend&amp;rdquo;. I also had a mixed performance experience, but this was &amp;ldquo;pre Cog&amp;rdquo; and Magma has also surely evolved lots since then, and I am not sure we did everything the way we should have either.&lt;/p>
&lt;p>SandstoneDB could also be interesting to look more closely at, but since I have been working with &lt;a href="http://www.nicolas-petton.fr" target="_blank" rel="noopener noreferrer">Nicolas Petton&lt;/a>
 on improving &lt;a href="http://smalltalkhub.com/#!/~gokr/Phriak" target="_blank" rel="noopener noreferrer">Phriak&lt;/a>
 (Riak interface for Pharo) it was natural to take a look at one of his &amp;ldquo;under the radar&amp;rdquo; projects - &lt;a href="http://www.smalltalkhub.com/#!/~NicolasPetton/Oak" target="_blank" rel="noopener noreferrer">Oak&lt;/a>
, an &amp;ldquo;OODBish&amp;rdquo; solution on top of Riak. At this point I have been doing much more than looking, in fact I am hacking on it! And oh, yeah, of course there are &lt;a href="http://wiki.squeak.org/squeak/512" target="_blank" rel="noopener noreferrer">lots more persistence options&lt;/a>
 available too.&lt;/p></description></item></channel></rss>