OrientDB Community Still Showing Signs of Life
OrientDB, a NoSQL database management system written entirely in Java, is finally gaining some much deserved traction. A recent OrientDB Google groups post welcomed Luca Molino and Andrey Lomakin as the first two commeitters to the open source project. The Orient team recognizes that . . .
It's surprising to find that the project's long history still hasn't culminated in a production-ready tool (according to Alex Popescu, OrientDB is still considered experimental).
According to the Orient website, the original engine was developed in C++ back in 1998, and has since grown into its new, "totally rewritten" Java version. This new version combines features from an array of sources, including Object Databases, Graph DBMS and cutting edge NoSQL engines. This results in a very fast, easily installed DBMS. For those wanting to learn more about OrientDB, the team has put together an in-depth wiki.
The most common [reason] why applications scale-out [is so bad], [is due to] the database. [The] database is the bottleneck of most of applications. OrientDB scales out very well on a single machine. A single server [of OrientDB handles the same] work [as] about 125 servers running MySQL. --OrientDB Project
It's surprising to find that the project's long history still hasn't culminated in a production-ready tool (according to Alex Popescu, OrientDB is still considered experimental).
According to the Orient website, the original engine was developed in C++ back in 1998, and has since grown into its new, "totally rewritten" Java version. This new version combines features from an array of sources, including Object Databases, Graph DBMS and cutting edge NoSQL engines. This results in a very fast, easily installed DBMS. For those wanting to learn more about OrientDB, the team has put together an in-depth wiki.
Comments
Eric Samson replied on Tue, 2012/01/17 - 3:52am
Alfonso Focareta replied on Tue, 2012/01/17 - 4:46am
Luca Garulli replied on Tue, 2012/01/17 - 5:05am
But wasn't OrientDB a ODBMS?
Orient ODBMS was the very first version of the Orient engine developed in C++ in 1998. Today OrientDB has been totally rewritten in Java under the form of a Document database but with the previous main goal: performance. However now you can find the Object Database, but it's a wrapper built on top of the Document Database. It maps transparently OrientDB document records with POJOs.
Mitch Pronschinske replied on Tue, 2012/01/17 - 5:02pm
in response to:
Luca Garulli
That's not to say it can't be used in production. As others have mentioned, I think people are unaware that OrientDB does have some production users. I think the Javalobby audience should definitely be aware of OrientDB and the unique opportunities it provides.
Luca Garulli replied on Tue, 2012/01/17 - 7:47pm
in response to:
Mitch Pronschinske
For those that think OrientDB community is born yesterday I can say that it has more than 15 contributors (8 the most actives) that in the last 2 years have contributed with several patches, new implementations and modules. Look at the Issue tracker.
Till some days ago all the changes were committed always by the Project Leader (me) because the review of the code was mandatory to always guarantee the best performance and usage of low memory. Not all the developers give the same importance to the performance, but in OrientDB project it's a must.
What is changed in the last days is that the two new committers (Luca and Andrey) after more than 1 year of experience working every day inside the OrientDB Engine and more than 30 contributions sent each (!) they earned the committer role.
Not all the Open Source projects have the same value for the "committer" role :-)
Mark Unknown replied on Tue, 2012/01/17 - 9:22pm
Some people just have higher standards than others. I remember about 10 years ago an XML/Object binder, I think it was Castor, that went years before it reached 1.0. But it still was production ready and well used in production.
One thing I would like to see is a Spring Data project for OrientDB. I want to be able to do the same sorts of things are being done for Neo4J. When i get to a point where i am going to use a Graph DB (or Document DB), and there isn't anything in Spring Data still, I guess I will have to pull my weight and jump in.