BT

Your opinion matters! Please fill in the InfoQ Survey!

StrokeDB, Just Another Distributed Database? Not Really.

| by Sebastien Auvray Follow 0 Followers on Apr 22, 2008. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

As Distributed Databases get more and more interest, implementations are flourishing. CouchDB showed the way to go and is now incubated as an Apache project. RDDB was one of the first Document-Oriented Distributed Databases implemented in Ruby. StrokeDB is a new actor in the scene. It was written by Yurii Rashkovskii and Oleg Andreev, who did a presentation at Euruko2008 (PDF slides). From the StrokeDB website:
StrokeDB is an embeddable distributed document database written in Ruby. It is schema-free, it scales infinitely, it even tracks revisions and perfectly integrates with Ruby applications.
StrokeDB is only 3 months old and offers already many interesting features, the basic ones for Distributed Databases:
  • Flat address space of documents identified by UUIDs.
  • JSON, schemaless document format.
  • References to other documents with automatic eager loading on access.
And some others that could differentiate itself from its competitors:
  • Documents revision control with diff/merge facilities built-in.
  • A flexible object-oriented API.
  • Simple search index over document slots.
  • Possibility to write native code for very specific performance issues.
Many more features are in the pipeline.

There's also a promise to port StrokeDB to thin client languages (JavaScript, ActionScript, etc.) to enable offline work with the data.

You can check out the StrokeDB code at GitHub and have a look at Yurii's short introduction to StrokeDB. While the authors are busy writing a clean API and adding new features, it will be interesting to see how the project evolves with maturity and later to have a look at benchmarks to check how it performs.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

What problem are we solving here? by Eugene Tolmachev

Can someone explain what problems are we solving here?

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT