Production ready yet?

OrientDB finally gets 1.0 release

Chris Mayer

The ‘deeply scalable’ document-graph database has long been lurking around, but after length delays finally

After spending a year on the sidelines, the team behind deeply
scalable document-graph DBMS OrientDB have awoken from the
perceived dormancy to deliver OrientDB 1.0 – a monumental moment in
their history.

‘ open source, 100% pure-Java NoSQL database
management system was one of the first onto the case for the
next-generation of database models, initially releasing the Java
version back in 2010. You can go back even further to 1998 for the
first appearance of OrientDB based on C++. Surprisingly despite
being around for a long time and having a very committed community,
OrientDB has yet to reach a stable 1.0 version. Until now.

Google Groups announcement
details what is new in this version,
whilst also thanking the team of 17 community members as well as
the four core committers. Changes include
a new Multi-Master
 architecture and
a new lightweight Object Database interface
which is better equipped to handle lazy loading. We can expect
improved OSGi support as well as more than 40 bugs

OrientDB is primed to deal with huge amounts of documents, being
that it forms the core of Orient products. The team have made
bold claims before, saying that ‘A single server [of OrientDB
handles the same] work [as] about 125 servers running MySQL’ and
their website claims that it can store up
150,000 documents per second, or
10 billion documents per day. A
mind-boggling amount.

The flexibility in working with OrientDB is vast as well –
it handles ACID transactions, indexing, fluent, and
SQL-like queries and can also work in schema-full, schema-less or
somewhere in between mode. It’s web ready through HTTP,
RESTful and JSON.

In a way we’re glad they’ve taken a long time to mull over the
product – it really is a wonderful piece of work, lovingly crafted
and not pushed out as an express product. We just hope it can gain
the traction and adoption it rightly deserves. Neo4j remains king
in the graph NoSQL ballpark currently, can OrientDB usurp it?
Download it here at
the Google Code home and you’d be wise to read the Getting
guide before jumping in too quickly.

comments powered by Disqus