InfoQ

News

StrokeDB, Just Another Distributed Database? Not Really.

Posted by Sebastien Auvray on Apr 22, 2008 10:15 AM

Community
Ruby
Topics
Data Access,
Database Design
Tags
Database
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.

1 comment

Reply

What problem are we solving here? by Eugene Tolmachev Posted Apr 30, 2008 11:08 AM
  1. Back to top

    What problem are we solving here?

    Apr 30, 2008 11:08 AM by Eugene Tolmachev

    Can someone explain what problems are we solving here?

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.