BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person or online.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or online.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News StrokeDB, Just Another Distributed Database? Not Really.

QCon San Francisco (Oct 2-6, 2023): Find real-world practical inspiration from senior software engineers.

StrokeDB, Just Another Distributed Database? Not Really.

This item in japanese

Bookmarks

Apr 22, 2008 1 min read

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
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
Style

This content is in the Dynamic Languages topic

Related Topics:

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.

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

Community comments

  • What problem are we solving here?

    by Eugene Tolmachev,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Can someone explain what problems are we solving here?

    Back to top

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

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

BT