OrientDB Distributed Graph Database http://orientdb.com OrientDB is a Multi-Model NoSQL Database with a true Graph engine Fri, 06 May 2016 14:49:46 +0000 en-US hourly 1 How to calculate maximum amount of memory consumed by OrientDB http://orientdb.com/memory-consumed-by-orientdb/ http://orientdb.com/memory-consumed-by-orientdb/#comments Tue, 26 Apr 2016 12:17:42 +0000 http://orientdb.com/?p=13920 April 26, 2016 By Andrey Lomakin, Lead Research & Development Engineer at OrientDB. Many users ask how much memory is consumed by OrientDB and which settings affect this. […]

The post How to calculate maximum amount of memory consumed by OrientDB appeared first on OrientDB Distributed Graph Database.

]]>
April 26, 2016

By Andrey LomakinLead Research & Development Engineer at OrientDB.

Many users ask how much memory is consumed by OrientDB and which settings affect this. This question becomes even more pertinent since the OrientDB 2.2 release. In this latest release, we allocate memory in big chunks (about of 1gb size each) and then split it between threads on demand.

There are 2 reasons why we have chosen this approach:ram logo

  1. To fix OS allocation issues like this one
  2. To prepare for the change when we assign adjacent memory chunks for each thread on demand. As an example, lets suppose the first thread got a page with address 0x1 but second thread got a page with address 0xFE. Then on the next request for a new page the first thread will get a page with address 0x2 and second thread will get a page with address 0xFF. We hope It will allow us to improve system performance because of better CPU cache locality feature usage.

So how do you calculate maximum amount of memory consumed by OrientDB?  The answer to that is simple.  OrientDB uses both heap and direct memory. Direct memory is used in disk cache and database journal.

Memory consumed by disk cache may be calculated looking at the value of the storage.diskCache.bufferSize configuration parameter, which shows the maximum amount of memory consumed by disk cache in megabytes. The page cache size in kilobytes may be retrieved by reading the value of the storage.diskCache.pageSize parameter. It may be done using the console CONFIG GET command for example.  

You may get the maximum amount of pages consumed by the database journal by reading the value of the storage.wal.cacheSize parameter. You should increase this value by 1 and multiply by the value of the storage.diskCache.pageSize parameter. In this way you will get the maximum amount of direct memory consumed by the database journal.  After that we need to add both calculated values and increase the result until not divisible by 1GB without reminder.

The rest is simple. Add the value which you calculated above and add the amount of memory consumed by heap and you will get the maximum amount of memory which will be consumed by OrientDB.

UPDATE 1: Maximum size of memory chunk in bytes which will be allocated by OrientDB may be set using the memory.chunk.size property.

If you have any questions about this blog entry or about any of OrientDB’s features please post your question on stackoverflow and we will answer it.  For a complete guide on OrientDB’s features and properties be sure to read our Documentation.

 

The post How to calculate maximum amount of memory consumed by OrientDB appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/memory-consumed-by-orientdb/feed/ 0
Released OrientDB 2.1.15 http://orientdb.com/released-orientdb-2-1-15/ http://orientdb.com/released-orientdb-2-1-15/#comments Mon, 04 Apr 2016 13:02:39 +0000 http://orientdb.com/?p=13883 London, April 4, 2016 The OrientDB Team has just released OrientDB v2.1.15, resolving 8 issues from v2.1.14. This is the last stable release. Please […]

The post Released OrientDB 2.1.15 appeared first on OrientDB Distributed Graph Database.

]]>
London, April 4, 2016

The OrientDB Team has just released OrientDB v2.1.15, resolving 8 issues from v2.1.14. This is the last stable release. Please upgrade your production environments to v2.1.15. For more information, take a look at the Change Log.

Download OrientDB v2.1.15 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.15 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-15/feed/ 0
Released OrientDB 2.1.14 http://orientdb.com/released-orientdb-2-1-14/ http://orientdb.com/released-orientdb-2-1-14/#comments Thu, 31 Mar 2016 07:57:52 +0000 http://orientdb.com/?p=13845 London, March 31, 2016 The OrientDB Team has just released OrientDB v2.1.14, resolving 22 issues from v2.1.13. This is the last stable release. Please […]

The post Released OrientDB 2.1.14 appeared first on OrientDB Distributed Graph Database.

]]>
London, March 31, 2016

The OrientDB Team has just released OrientDB v2.1.14, resolving 22 issues from v2.1.13. This is the last stable release. Please upgrade your production environments to v2.1.14. For more information, take a look at the Change Log.

Download OrientDB v2.1.14 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.14 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-14/feed/ 0
OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace http://orientdb.com/orientdb-on-centurylink-cloud/ http://orientdb.com/orientdb-on-centurylink-cloud/#comments Thu, 17 Mar 2016 10:37:16 +0000 http://orientdb.com/?p=13750 OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace   LONDON, UK – March 17, 2016 – OrientDB, the pioneer behind […]

The post OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace appeared first on OrientDB Distributed Graph Database.

]]>
OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace

 

LONDON, UK – March 17, 2016 OrientDB, the pioneer behind the world’s first Open Source, NoSQL distributed graph-document database, today announced its certification under the CenturyLink Cloud Marketplace Provider Program. Through this partnership, CenturyLink Cloud users are now able to deploy and manage OrientDB’s community or enterprise edition databases via CenturyLink’s Blueprints library.

OrientDB is a second-generation distributed graph database with the flexibility of documents and an open source Apache 2 license. By treating every vertex and edge as a JSON (JavaScript Object Notation) document, OrientDB enables the creation of multi-directional property graphs, allowing bulks of data to be traversed with ease. This new multi-model approach, with a polyglot engine, eliminates the need for multiple systems, ensures data consistency and optimizes the formation of complex relationships. Even for a document-based database, the relationships are managed, as in graph databases, with direct connections amongst records. Its versatility and rapid integration makes OrientDB a perfect candidate for use cases ranging from recommendation engines and fraud detection to real-time analytics and content management. Fortune 500 companies, government entities and startups all use the technology to build large-scale innovative applications.

CenturyLink Cloud customers can now benefit from OrientDB’s features:

  • All-in-one graph, document and object store database
  • Stores 220,000 records per second on common hardware
  • ACID (atomicity, consistency, isolation and durability) compliant
  • Support for HTTP and JSON
  • Supports schema-less, schema-full and schema-mixed modes
  • Strong security profiling system based on user and roles
  • Despite being a NoSQL database, it still supports SQL amongst the query languages, making it familiar to those coming from a relational database background
  • Supports multi-master replication

OrientDB Community Edition is free for any purpose (including commercial use). OrientDB Enterprise Edition serves as an extension of the Community Edition by providing enterprise-needed features such as: Query Profiler, distributed clustering configuration, metrics recording, and Live Monitor with configurable alerts.

The CenturyLink Cloud Marketplace Provider Program allows participating technology companies, like OrientDB, to integrate with the CenturyLink Cloud platform. These additional business-ready solutions are available to CenturyLink’s cloud, hosting and network customers.

“Companies hoping to leverage big data are getting tired of dealing with multiple systems and increasing infrastructural costs,” said Luca Garulli, CEO of OrientDB. “Customers choose OrientDB for its innovative Multi-model database capabilities and affordable nature. Expanding our capabilities to the cloud through CenturyLink provides the perfect accessible solution without the need for multiple database systems or costly servers.”

“The foundation of the big data revolution on our platform has been software innovation around unstructured data management,” said David Shacochis, vice president of platform enablement at CenturyLink, “OrientDB is a great example of this trend, allowing our customers to manage their unstructured data relations in a scalable model that drives insight out of their business workloads”

To start using OrientDB on CenturyLink Cloud today, refer to the “Getting Started” guide on the CenturyLink Cloud Knowledge Base.

About OrientDB

OrientDB is an open source 2nd Generation Distributed Graph Database with the flexibility of Documents and a familiar SQL dialect. With downloads exceeding 70,000 per month, more than 100 community contributors and 1000’s of production users, OrientDB is experiencing tremendous growth in both community and Enterprise adoption. First generation Graph Databases lack the features that Big Data demands: multi-master replication, sharding and more flexibility for modern complex use cases. See for yourself, Download OrientDB and give it a try.

Editorial Contacts:
Paolo Puccini
OrientDB Ltd
+44 203 3971 609
info@orientdb.com

The post OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-on-centurylink-cloud/feed/ 0
Released OrientDB 2.1.13 http://orientdb.com/released-orientdb-2-1-13/ http://orientdb.com/released-orientdb-2-1-13/#comments Tue, 15 Mar 2016 09:12:32 +0000 http://orientdb.com/?p=13732 London, March 15, 2016 The OrientDB Team has just released OrientDB v2.1.13, resolving 16 issues from v2.1.12. This is the last stable release. Please […]

The post Released OrientDB 2.1.13 appeared first on OrientDB Distributed Graph Database.

]]>
London, March 15, 2016

The OrientDB Team has just released OrientDB v2.1.13, resolving 16 issues from v2.1.12. This is the last stable release. Please upgrade your production environments to v2.1.13. For more information, take a look at the Change Log.

Download OrientDB v2.1.13 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.13 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-13/feed/ 0
OrientDB Teleporter – Making Migrations Easier (Part 2) http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/ http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/#comments Mon, 14 Mar 2016 14:50:39 +0000 http://orientdb.com/?p=13692 By OrientDB Developer Gabriele Ponzi Teleporter to Sync your DB and OrientDB This is Part 2 of our step by step guide on how to […]

The post OrientDB Teleporter – Making Migrations Easier (Part 2) appeared first on OrientDB Distributed Graph Database.

]]>
By OrientDB Developer Gabriele Ponzi

Teleporter to Sync your DB and OrientDB

This is Part 2 of our step by step guide on how to use Teleporter to migrate and synchronize your database with OrientDB.

If you are interested in a detailed description of the tool, of its inner workings and features, please read the previous post (part 1) or the official documentation.

In short, OrientDB Teleporter is a tool that synchronizes a RDBMS to an OrientDB database. You can use Teleporter to:

- Import your existing RDBMS to OrientDB.

- Keep your OrientDB database synchronized with changes from the RDBMS. In this case the database on RDBMS remains the primary one and the database on OrientDB a synchronized copy. Synchronization is one way, so all the changes in the OrientDB database will not be propagated to the RDBMS.

This means that the first execution process performs a migration from scratch, whereas all subsequent migrations on the same target OrientDB graph database carry out a synchronization between your source database and OrientDB.
This dual behaviour is transparent to the user who will always follow the same procedure.

Teleporter is fully compatible with several RDBMS that have a JDBC drivers: we successfully tested Teleporter with Oracle, SQLServer, MySQL, PostgreSQL and HyperSQL. Teleporter manages all the necessary type conversions between the different DBMSs and imports all your data as a Graph in OrientDB.
This tool is really easy to use thanks to a completely automatic and clear execution which require few important parameters. At the same time, it’s possible to enrich the migration process by specifying different strategies and customizations which allow you to obtain more refined results.

Now let’s start from the simplest migration case. First of all, you can invoke the tool through  the oteleporter.sh (Unix and OS X platforms) or oteleporter.bat (Windows platforms) scripts. Then you must type 3 mandatory arguments to begin your import:

- -jdriver: is the driver name of the DBMS from which you want to execute the import.

- -jurl: is the JDBC URL giving the location of the source database to import.

- -ourl: is the URL for the destination Orient graph database.

 If credentials are required to access your source database you have to type two  more arguments:

- -juser: is the username to access the source database.

- -jpasswd is the password to access the source database.

Thus, in this case the generic call to Teleporter looks like this:

oteleporter.sh -jdriver <jdbc-driver> -jurl <jdbc-url> -juser <username>

-jpasswd <password> -ourl <orientdb-url>

 

All other parameters are optional: now let’s start with a standard migration from each compatible DBMS.

When you specify the DBMS you want to connect with through the argument -jdriver, you must choose amongst the following values:

- Oracle

- SQLServer

- MySQL

- PostgreSQL

- HyperSQL

N.B.: the driver identification is not case sensitive, so you may also type  “oracle”, “sqlserver” etc.

Migrating and Syncing with your database

Let’s suppose we want to import the source database “source-db”  into an OrientDB graphDB called “myTargetDB” and that the source database relies on our local machine with credentials admin|admin.
Depending on our specific DBMS we’ll type the different commands reported in the following table:

DBMS

SOURCE DB URL FORMAT

TELEPORTER COMMAND

Oracle

jdbc:oracle:thin:@<HOST>:<PORT>:<SID>

oteleporter.sh -jdriver Oracle

-jurl jdbc:oracle:thin:@localhost:1521:xe
-juser admin -jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB

SQLServer

jdbc:sqlserver://<HOST>:<PORT>;databaseName=<DB>
oteleporter.sh -jdriver SQLServer

-jurl jdbc:sqlserver://localhost:1433;databaseName=source-db
-juser admin-jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB
(*)

MySQL

jdbc:mysql://<HOST>:<PORT>/<DB>
oteleporter.sh -jdriver MySQL

-jurl jdbc:mysql://localhost:3306/source-db
-juseradmin -jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB

PostgreSQL

jdbc:postgresql://<HOST>:<PORT>/<DB>
oteleporter.sh -jdriver PostgreSQL

-jurl jdbc:postgresql://localhost:5432/source-db
-juser admin -jpasswd admin
 -ourl /ORIENTDB_HOME/databases/myTargetDB

HyperSQL

jdbc:hsqldb:hsql://<HOST>/<DB>

(connection to a database server)

jdbc:hsqldb:file:<filepath>,
jdbc:hsqldb:mem:<DB>,
jdbc:hsqldb:res:<package name>

(connection to a resource)

oteleporter.sh -jdriver HyperSQL

-jurl jdbc:hsqldb:hsql://localhost/source-db
-juser admin-jpasswd admin
 -ourl /ORIENTDB_HOME/databases/myTargetDB

(*) If the source database contains spaces in the name you have to use a URL like this:
“Source DB” →  -jurl “jdbc:sqlserver://localhost:1433;databaseName={Source DB};”

Next, we must simply wait for the process to end.

Migration with optional parameters

If you want to enrich the migration process from your specific DBMS with optional parameters, you just have to type them following the syntax described in the documentation and in the previous post [link].
Here I report the complete command syntax:

oteleporter.sh -jdriver <jdbc-driver> -jurl <jdbc-url> -ourl <orientdb-url>

[-juser <username>] [-jpasswd <password>] [-s <strategy>]
[-nr <name-resolver>] [-v <verbose-level>]
([-include <table-names>] | [-exclude <table-names>])
[-inheritance <orm-technology>:<ORM-file-url>]

 

I hope this post was helpful and interesting.

Stay tuned,

Gabriele Ponzi
OrientDB Ltd

Download OrientDB Teleporter!

References:
Teleporter full documentation: https://github.com/orientechnologies/orientdb-labs/blob/master/Teleporter-Index.md

 

 

The post OrientDB Teleporter – Making Migrations Easier (Part 2) appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/feed/ 0
OrientDB Teleporter – Making Migrations Easier (Part 1) http://orientdb.com/orientdb-teleporter-making-migrations-easier/ http://orientdb.com/orientdb-teleporter-making-migrations-easier/#comments Wed, 09 Mar 2016 15:32:17 +0000 http://orientdb.com/?p=13636 By OrientDB Developer Gabriele Ponzi Big Data is an important topic nowadays. The large amount of data and their unstructured and heterogeneous nature have exposed […]

The post OrientDB Teleporter – Making Migrations Easier (Part 1) appeared first on OrientDB Distributed Graph Database.

]]>
By OrientDB Developer Gabriele Ponzi

Big Data is an important topic nowadays. The large amount of data and their unstructured and heterogeneous nature have exposed the limitations of the relational database model.

In order to restrict these barriers in recent years, the NoSQL movement was born, which proposed new procedural and architectural approaches. Among these technologies are graph databases, innovative databases which organize and manage information in a graph structure, applied in the representation of complex networks such as social ones.

For these reasons, more and more people are intrigued by products like OrientDB.

Teleporter’s Answer to the Migration Problem

Despite the wide variety of new solutions, we are often reluctant to switch to new technologies for several reasons. First of all, migration from the old DB to the new one. Migration requires substantial costs and takes considerable time, because the task is usually commissioned to specialized companies who perform it manually and individually for the customer.

This reality prompted the OrientDB team to develop Teleporter. Teleporter is a  free tool which allows an automated and quick migration from a relational database to the OrientDB graph database.

Teleporter was conceived to satisfy various requirements:

- Ensure high versatility, in order to make the import ductile and effective for different use cases.

- Provide a low configuration level, in order to be quickly usable, and offer a certain degree of customization to the process by making available different strategies and approaches that allow to overcome the automatic nature of the tool.

- Ensure high scalability.

Problem: How can we achieve an automatic migration between two DBMSs that manage data in different ways? The answer is by defining an effective and efficient mapping between the two models in question: the relational and the graph model.

The whole process consists of 4 phases:

1. Source DB Schema Building (E-R model): the source DB schema is built by querying the source DB metadata.

2. Graph Model Building: a correspondent and coherent Graph Model is built.

3. OrientDB Schema Writing: the OrientDB schema is written according to the Graph Model just built.

4. OrientDB importing: importing data from the source DB to the graph database of OrientDB.

 

OrientDB Teleporter's effective and efficient mapping between two models

 

Below is an OrientDB Teleporter execution dump:

Execution Strategies

The Graph Model’s expressive power allows it to perform various optimizations based on the aggregation of data. For this reason, Teleporter provides two different import strategies:

- naive strategy

- naive-aggregate strategy

The naive strategy follows a direct transformation approach between the E-R model of the source DB and the correspondent Graph Model, in which:

- Each Entity (or Table) with its attributes is converted in a “Vertex-Type” (an OrientDB vertex class).

- Each Relationship between two entities is converted in a “Edge-Type” (an OrientDB edge class).

OrientDB Teleporter - direct transformation approach

This strategy is fast and requires less transformation rules. Nevertheless, a certain degree of redundancy is permitted.

As you can see in the following example, in the relational model- the only function of the film_actor join table is to represent a many-to-many relationship between movies and actors, which in OrientDB has been converted into a Vertex-Type.

OrientDB Teleporter - vertex type relationshipsThus the second strategy aggregates complex relationships into “aggregator-edges”, simplifying the structure of the resulting graph model.

In this way, even if this strategy requires more transformation rules, we obtain an overhead reduction and better performance on the graph imported in OrientDB.

OrientDB Teleporter - aggregated complex relationships

The following example show how two different strategies can be used on the same source DB to aggregate data.  On the left a naive translation of tables and on the right, an optimized naive-aggregate solution.

 

OrientDB Teleporter - direct transformation approach (2)

Sequential executions and one-way Synchronizer

Teleporter is conceived to support many sequential executions from the same source DB to the same graph DB of OrientDB, in this way you can:

- Personalize your import, combining the different strategies and settings by including or excluding the chosen tables and by running Teleport more times in order to obtain a more complex and customized import strategy.

- Use it as a one-way synchronizer and maintain a copy of your DB: all the changes applied to the source DB (primary DB) are propagated to the imported graph DB, but not vice versa.

OrientDB Teleporter - read write operationsThus if you want that your data remain synchronized you have to perform the write operations only on the primary database, but you can perform the reads on both databases.

Other features

Teleporter currently offers other features adoptable during the import process:

- Inheritance relationships inference

- Filters based on white-list and black-list policies

- Autorename of all elements in the source DB according to the Java convention

- Driver JDBC auto-configuration

- Output Manager with 5 different verbosity levels

These will be shown and discussed in the next posts.

Usage Example

Teleporter is a tool written in Java, but it can be used as a tool thanks to the teleporter.sh script (or .bat on Windows).

oteleporter.sh -jdriver <jdbc-driver> -jurl <jdbc-url> -ourl <orientdb-url>

[-juser <username>] [-jpasswd <password>] [-s <strategy>]
[-nr <name-resolver>] [-v <verbose-level>]
([-include <table-names>] | [-exclude <table-names>]
[-inheritance <orm-technology>:<ORM-file-url>]

 

The main arguments necessary for migration are:

- -jdriver is the driver name of the DBMS from which you want to execute the import.

- -jurl is the JDBC URL giving the location of the source DB to import.

- -juser is the username to access the source DB.

- -jpasswd is the password to access the source DB.

- -ourl is the URL for the destination Orient graph DB.

Through the argument “-s” we can choose the strategy adopted during the importing phase. If not specified, naive-aggregate strategy is adopted. Possible values:

- Naive: performs a “naive” import of the data source. The data source schema is translated semi-directly in a correspondent and coherent graph model.

- Naive-aggregate: performs a “naive” import of the data source. The data source schema is translated semi-directly in a correspondent and coherent graph model using an aggregation policy on the join tables.

In the following example, we’ll import the source DB “testdb” from a PostgreSQL DBMS to OrientDB through the naive strategy:

oteleporter.sh -jdriver postgresql -jurl jdbc:postgresql://localhost:5432/testdb

-juser username -jpasswd password
-ourl plocal:$ORIENTDB_HOME/databases/testdb
-s naive

Compatibilities

Teleporter is compatible with all the RDBMS that have a JDBC driver. We have  successfully tested Teleporter with:

- Oracle (last tested version: 12c)

- SQLServer (last tested version: SQLServer 2014)

- MySQL (last tested version: 5.1.35)

- PostgreSQL (last tested version: 9.4-1201)

- HyperSQL (last tested version: 2.3.2)

Teleporter manages all the necessary type conversions for these DBMSs during the import process.

Stay tuned,

Gabriele Ponzi
OrientDB Ltd

Download OrientDB Teleporter!

References:
Teleporter full documentation: https://github.com/orientechnologies/orientdb-labs/blob/master/Teleporter-Index.md

The post OrientDB Teleporter – Making Migrations Easier (Part 1) appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-teleporter-making-migrations-easier/feed/ 0
Released OrientDB 2.1.12 http://orientdb.com/released-orientdb-2-1-12/ http://orientdb.com/released-orientdb-2-1-12/#comments Wed, 02 Mar 2016 09:42:18 +0000 http://orientdb.com/?p=13597 London, March 2, 2016 The OrientDB Team has just released OrientDB v2.1.12, resolving 16 issues from v2.1.11. This is the last stable release. Please […]

The post Released OrientDB 2.1.12 appeared first on OrientDB Distributed Graph Database.

]]>
London, March 2, 2016

The OrientDB Team has just released OrientDB v2.1.12, resolving 16 issues from v2.1.11. This is the last stable release. Please upgrade your production environments to v2.1.12. For more information, take a look at the Change Log.

Download OrientDB v2.1.12 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.12 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-12/feed/ 0
Stay Tuned For Our OrientDB v2.2 Beta Announcement! http://orientdb.com/orientdb-beta-teaser/ http://orientdb.com/orientdb-beta-teaser/#comments Wed, 17 Feb 2016 16:47:33 +0000 http://orientdb.com/?p=13478 OrientDB v2.2 Beta Going Live Next Week!   We’ve worked hard on it,  it’s about to go live, we can’t contain our excitement, and of […]

The post Stay Tuned For Our OrientDB v2.2 Beta Announcement! appeared first on OrientDB Distributed Graph Database.

]]>
OrientDB v2.2 Beta Going Live Next Week!

 

We’ve worked hard on it,  it’s about to go live, we can’t contain our excitement, and of course, we couldn’t have done it without you!

 

OrientDB Labs

For the past few years all of us here at OrientDB have strived to deliver a fresh, innovative platform on which enterprises could work on to enrich their business.  We’ve always been proud of our work, and it’s been a real pleasure to collaborate with and learn from an ever growing community of dedicated developers.

With the launch of OrientDB back in 2011 we breathed some fresh air into the DBMS landscape, making waves with our multi-model approach (to the delight of some and shock of others). From then on it’s been a rollercoaster of a ride and in 2015 we continued to disrupt the market and climb the DBMS charts.  We’re hoping 2016 will be no different, and in that spirit we are launching our 2.2 Beta version of OrientDB in the next few days **queue the drum roll**

We couldn’t have achieved this without the ever growing community of developers who worked tirelessly alongside our team.  Of course, this is a Beta release so not suitable for production environments but we’re hoping our community is just as excited as we are with the announcement, and we’re looking forward to working together to test what we think will be our best release so far.

Our engineers have been working hard to make OrientDB even better and we’ve loaded version 2.2 full of new features which we’re sure you’ll love too.  The main focus of this version is on Security, APIs and performance, building on our distributed capabilities as well as graph enhancements.  We’ve added new features such as Teleporter, which introduces a simple, straightforward way to convert your relational databases to OrientDB.  Other new features include:

  • OrientJS: Native unmarshaling of requests by using C++ code
  • Improved auditing and authentication, password salt and data-at-rest encryption
  • New OrientDB Studio now replaces the workbench, adding a new architecture and new modules
  • New configurable Graph Consistency to speed-up change operations against graphs
  • And so much more (We wouldn’t want to spoil the fun and want to keep some of these under wraps until the official beta release!)

 

During the coming days, we’ll be discussing several of the new features here in our company blog so stay tuned for more on each of OrientDB’s new capabilities and enhancements.  Once we’re live, go ahead and take if for a test drive and let us know what you think.  For a complete list of features please refer to our OrientDB v2.2 documentation following the Beta launch.

Thank you to our community and looking forward to receiving your feedback!

 

Luca Garulli

Chief Executive Officer, Founder

The post Stay Tuned For Our OrientDB v2.2 Beta Announcement! appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-beta-teaser/feed/ 0
Released OrientDB 2.1.11 http://orientdb.com/released-orientdb-2-1-11/ http://orientdb.com/released-orientdb-2-1-11/#comments Mon, 15 Feb 2016 17:08:39 +0000 http://orientdb.com/?p=13465 London, February 15, 2016 The OrientDB Team has just released OrientDB v2.1.11, resolving 12 issues from v2.1.10. This is the last stable release. Please […]

The post Released OrientDB 2.1.11 appeared first on OrientDB Distributed Graph Database.

]]>
London, February 15, 2016

The OrientDB Team has just released OrientDB v2.1.11, resolving 12 issues from v2.1.10. This is the last stable release. Please upgrade your production environments to v2.1.11. For more information, take a look at the Change Log.

Download OrientDB v2.1.11 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.11 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-11/feed/ 0