NoSQL with Java: A breakthrough for OrientDB
OrientDB 2.0 has brought a number of nifty new features and polished up the user experience.
The second major version of the Java NoSQL database, OrientDB has reached its first milestone. The announcement promises performance improvements, optimized user experience and a lot of “innovative new features”.
The web application “Studio” now comes with extended NoSQL tooling, for example a graph editor (see image below). Overall, the project manager Luca Garulli and his team endeavored to create a better user experience. Revised documentation was also part of the improved user experience package.
In the ‘Security Manager’ users can be assigned to different roles and rights:
ETL, Asynchronous graph, new SQL functions
With the new ETL function (Extract Transform Load), the task of importing databases has been simplified. To do this, all you need is a JSON file and the Command Tool OETL.
In Graph API the feature OrientGraphAsynch was implemented as an experiment. The second level cache was removed and the scheme concurrency was improved. In the SQL pane, the function UUID () was added. This can create Unique IDs and new statistical functions such as mode (), variance (), stddev (), median () and percentile ().
The version is downward compatible. If you want to enjoy the newly added binary serialization, you have to export the database and then reimport it. A guide to migration from the previous version 1.7.x to 2.0 is available on GitHub. The community edition software with an Apache 2 license can be downloaded from the project website.
OrienTechnologies began in the late 90s. It is a scalable, document-based database management system (DBMS) in Java (originally C++) for developers. OrientDB was first released in 2010 and followed by version 1.0 in 2012. OrientDB can be operated in different modes; as a document database, as an Object Relational Mapper (ORM) or as a graph database with key-value data storage.