Text

OrientDB 1.0…1.1

I fell in love with #OrientDB first time I came across it.

What I like about OrientDB are the following:

  • A cool, high performance, #nosql DB.
  • You can use it in the flavor you prefer: Document DB, Object DB, Graph DB.
  • Use it Embedded, as a Server or Clustered.
  • A NOSQL DB that supports SQL (like) queries.
  • A liberal Apache2 license.

While 1.0 (around the corner) looks like an important milestone to reach, 1.1 that’s coming seems more exiting.

A list of some interesting features to come in version 1.1:

  • Data compression at storage level - Storage efficiency
  • Data repair tool - Will give some confidence should something go wrong in a production db
  • Lucene integration - Should improve performance
  • SSL support for binary & HTTP connections - Security during transmission is important.
  • Time Machine (revisions/versioning) - Can address some interesting use cases
  • Support for Stored procedures - We have applications with lot of things done as stored procedures (though I don’t like it), I expect support for stored procedures should make it easy to migrate to OrientDB.
  • And others: Views, Sub queries, VFS, …

    (Source: code.google.com)

    Text

    OrientDB

    What I Like:

    • A NoSQL Document Database that supports SQL, 
    • A friendly Apache 2.0 license.
    • Supports Schema-less & Schema-full or Mixed modes
    • Distributed & Transactional

    I’d have liked it better if:

    • There was SPARQL support.

    See: http://www.orientechnologies.com/

    Others I’m looking at: