OrientDB Multi-Model NoSQL Database http://www.orientechnologies.com OrientDB is a Multi-Model NoSQL Database with Graph and Document engine Wed, 04 Mar 2015 00:19:56 +0000 en-US hourly 1 Released OrientDB Enterprise 2.0.3, now FREE for Development! http://www.orientechnologies.com/released-orientdb-enterprise-2-0-3-now-free-development/ http://www.orientechnologies.com/released-orientdb-enterprise-2-0-3-now-free-development/#comments Thu, 26 Feb 2015 12:02:11 +0000 http://www.orientechnologies.com/?p=12413 London, February 26 2015 Orient Technologies is glad to announce that new OrientDB Enterprise 2.0.3. Starting from this release, the Enterprise Edition is FREE […]

The post Released OrientDB Enterprise 2.0.3, now FREE for Development! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, February 26 2015

Orient Technologies is glad to announce that new OrientDB Enterprise 2.0.3. Starting from this release, the Enterprise Edition is FREE for Development! With the Enterprise Edition users can take advantage of:

 

Download now OrientDB Enterprise Edition.

 

The post Released OrientDB Enterprise 2.0.3, now FREE for Development! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/released-orientdb-enterprise-2-0-3-now-free-development/feed/ 0
Released OrientDB 2.0.3 hotfix http://www.orientechnologies.com/released-orientdb-2-0-3-hotfix/ http://www.orientechnologies.com/released-orientdb-2-0-3-hotfix/#comments Fri, 20 Feb 2015 00:42:38 +0000 http://www.orientechnologies.com/?p=12364 London, February 20th, 2015 Orient Technologies released OrientDB 2.0.3 hotfix. Please upgrade your OrientDB 2.x version to this one. You can download it from […]

The post Released OrientDB 2.0.3 hotfix appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, February 20th, 2015

Orient Technologies released OrientDB 2.0.3 hotfix. Please upgrade your OrientDB 2.x version to this one.

You can download it from the official download page, or if you are using Maven update the dependency to:

<dependency>
  <groupId>com.orientechnologies</groupId>
  <artifactId>orientdb-graphdb</artifactId>
  <version>2.0.3</version>
</dependency>

 

The main issues resolved are on Distributed Architecture (Replication and Sharding). The full list is online.

Have fun with Graphs and Multi-Model,
Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB

http://about.me/luca.garulli

 

The post Released OrientDB 2.0.3 hotfix appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/released-orientdb-2-0-3-hotfix/feed/ 0
Released OrientDB 2.0.2 hotfix http://www.orientechnologies.com/released-orientdb-2-0-2-hotfix/ http://www.orientechnologies.com/released-orientdb-2-0-2-hotfix/#comments Mon, 09 Feb 2015 16:33:53 +0000 http://www.orientechnologies.com/?p=12327 London, February 9th, 2015 Orient Technologies released OrientDB 2.0.2 hotfix. Please upgrade your OrientDB 2.x version to this one. You can download it from […]

The post Released OrientDB 2.0.2 hotfix appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, February 9th, 2015

Orient Technologies released OrientDB 2.0.2 hotfix. Please upgrade your OrientDB 2.x version to this one.

You can download it from the official download page, or if you are using Maven update the dependency to:

<dependency>
  <groupId>com.orientechnologies</groupId>
  <artifactId>orientdb-graphdb</artifactId>
  <version>2.0.2</version>
</dependency>

 

The main issues resolved are on Distributed Architecture and WAL (Journal) file. The full list is online.

Have fun with Graphs and Multi-Model,
Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB

http://about.me/luca.garulli

 

The post Released OrientDB 2.0.2 hotfix appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/released-orientdb-2-0-2-hotfix/feed/ 0
OrientDB 2.0 is now Production Ready! http://www.orientechnologies.com/orientdb-2-0-production-ready/ http://www.orientechnologies.com/orientdb-2-0-production-ready/#comments Tue, 20 Jan 2015 18:12:11 +0000 http://www.orientechnologies.com/?p=12292 London, January 20, 2015 After 6 months of Development and Testing, 400+ Issues resolved, 55 Pull Requests from the Community, 3 Milestones and 2 […]

The post OrientDB 2.0 is now Production Ready! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, January 20, 2015

After 6 months of Development and Testing, 400+ Issues resolved, 55 Pull Requests from the Community, 3 Milestones and 2 Release Candidates, Orient Technologies is thrilled to announced the final release of OrientDB 2.0!

Thank you to the Orient Technologies Team and our amazing user Community whose hard work, contributions, requests and diligent testing made this release possible.

Download OrientDB v 2.0

Can I use OrientDB v2.0 in production?

Yes. We recommend using this final 2.0 over previous versions. OrientDB 2.0 supports databases created with release 1.7. In order to use the new binary serialization, you are required to export and re-import the database. For more information, take a look at Migrate from 1.7.x. Since the APIs have been improved upon for this release, we always recommend testing your database(s) and application(s) in a test environment before upgrading your production environment.

What’s new?

OrientDB 2.0 is much faster than 1.7 (many users notice a 40% performance improvement) and performs much better when distributed on multiple servers. The new Binary Protocol compresses the database size resulting in less space used on the File System and higher I/O throughput. Furthermore, OrientDB 2.0 is less sensitive to index corruption between restarts.

Below is a detailed list of the enhancements since 1.7:

Core:

  • Avoids rebuilding of indexes if working in Transactional mode
  • New Schema Driver Serialization avoids writing field names for records with Schema resulting in 20% performance improvement
  • New RW-Locks to speed-up internal parallelism
  • In-Memory database uses off-heap cache now
  • Disabled SNAPPY compression by default
  • Improved schema concurrency using immutable instances
  • Added strategies to manage conflict: by content and auto-merge. Furthermore can be injected custom strategy via Java API
  • Cache, removed 2nd level cache and improved 1st level cache
  • Cluster selection strategy now can decide on the input document content
  • Clusters can be detached (offline) and re-attached (online)
  • Better automatic allocation of Heap and Disk-Cache
  • Fetch-Plan: support for wildcards
  • Using SIGTRAP (kill -5) to dump OrientDB information
  • Logged database name on server and embedded messages
  • Removed a couple of internal layers on Document API to speedup and simplify implementation. Added also ODocument.fromMap() and ODocument.toMap()
  • Merged in core commons and native-os modules
  • On first run, the server asks for the root password. Blank means auto-generate (like before)
  • Global settings are copied in database at creation time and can be update
  • Lucene plugin for Full-Text and Spatial indexes is now in bundle with default distribution

 
Distributed:

  • 3x performance improvement
  • New asynchronous replication
  • On first run, ask for node name. Blank means auto-generate (like before)
  • Unified script and config files with stand-alone server

 
Javascript:

  • Invoking of JS functions is now 10x faster due to caching of the JVM Script engine

 
Network:

  • Support for stateless requests using Token

 
Graph API:

  • Disabled light-weight edges by default
  • New OGraphBatchInsertBasic and OGraphBatchInsert API for massive insertion on graphs: 13x faster than Blueprints
  • New SQL MOVE VERTEX command to refactor portion of graphs and to move vertices between distributed nodes
  • Improved OrientGraphFactory performance reducing recycling time. Added central config of generated graphs in Factory
  • Creation of edges can be set to avoid updating both vertices

 
Security:

  • Added configurable SSL to HTTP and binary connections

 
SQL:

  • New UUID() function to generate Unique IDs
  • New statistic functions: mode(), variance(), stddev(), median(), percentile()
  • Rewritten implementation of shortestPath() function to be much faster
  • Improvement for “order by @rid desc” to browse results in opposite direction without use an index or RAM
  • Added UNSAFE to CREATE PROPERTY command to avoid slow checks auto conversion from map when working on EMBEDDED types

 
Tools:

  • Studio: New Layout, new Graph Editor, new Security panel (Users and Roles management)
  • New ETL module to import data from JDBC, CVS and JSON input sources

 

Download OrientDB v 2.0

Have fun with graphs and documents,

Luca Garulli
CEO of Orient Technologies
the Company behind OrientDB
www.orientechnologies.com

The post OrientDB 2.0 is now Production Ready! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/orientdb-2-0-production-ready/feed/ 0
Second Release Candidate for OrientDB 2.0: another step toward the final v2.0 http://www.orientechnologies.com/orientdb-2-0-rc2/ http://www.orientechnologies.com/orientdb-2-0-rc2/#comments Tue, 13 Jan 2015 00:20:40 +0000 http://www.orientechnologies.com/?p=12274 London, January 13, 2015 A few hours ago, Orient Technologies released OrientDB 2.0-rc2 as the second Release Candidate before the Final 2.0. This version […]

The post Second Release Candidate for OrientDB 2.0: another step toward the final v2.0 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, January 13, 2015

A few hours ago, Orient Technologies released OrientDB 2.0-rc2 as the second Release Candidate before the Final 2.0. This version contains no enhancements, but rather 86 issues resolved from 2.0-rc1, which was released 3 weeks ago.

Please help us with testing OrientDB 2.0-rc2 so that we can release a stable OrientDB 2.0 in about 1 week.

Take a look at the full list of resolved issues.

 

Can I use OrientDB v2.0-rc2 in production?

No. This is not the final 2.0 version. This release is the second Release Candidate (RC stands for Release Candidate) of 2.0 on the path to the final version in the next days. We suggest using OrientDB v2.0-rc2 in development and test only. If you plan to go in production in less than a couple of weeks, we suggest staying with OrientDB 1.7.x. Otherwise, go ahead and use OrientDB 2.0-rc2.

 

Is 2.0-rc2 compatible with previous versions of OrientDB?

You can open any database created with past versions of OrientDB. In order to use the new binary serialization, you are required to export and re-import the database. For more information, take a look at Migrate from 1.7.x.

Download OrientDB v 2.0-rc2

Have fun with graphs & documents,

Luca Garulli
CEO of Orient Technologies
the Company behind OrientDB
www.orientechnologies.com

The post Second Release Candidate for OrientDB 2.0: another step toward the final v2.0 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/orientdb-2-0-rc2/feed/ 0
Released OrientDB 2.0-rc1! http://www.orientechnologies.com/released-orientdb-2-0-rc1/ http://www.orientechnologies.com/released-orientdb-2-0-rc1/#comments Wed, 17 Dec 2014 22:28:58 +0000 http://www.orientechnologies.com/?p=12239 London, December 17, 2014 Orient Technologies has released OrientDB 2.0-rc1 as the first Release Candidate before the Final 2.0. We implemented some enhancement requests, […]

The post Released OrientDB 2.0-rc1! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, December 17, 2014

Orient Technologies has released OrientDB 2.0-rc1 as the first Release Candidate before the Final 2.0. We implemented some enhancement requests, but more importantly, we resolved many issues reported by users in version 2.0-M3: 87 issues in total.

Please help us with testing OrientDB 2.0-rc1 so that we can release a stable OrientDB 2.0 in about 1-2 weeks.

- Core: Avoid forced rebuilding of indexes if working in Transactional mode
- Javascript: Invocation of JS functions is now 10x faster
- Network: Added support for stateless requests using a Token
- Graph API: Disabled light-weight edges by default
- Bug resolution: 87 total issues from 2.0-M3.

 

Take a look at the Full list of issues.

 

Can I use OrientDB v2.0-rc1 in production?

No. This is not the final 2.0 version. This release is the first Release Candidate (RC stands for Release Candidate) of 2.0 on the path to the final version in the next days. We suggest using OrientDB v2.0-rc1 in development and test only. If you plan to go in production in less than one month, we suggest staying with OrientDB 1.7.x. Otherwise, go ahead and use OrientDB 2.0-rc1.

 

Is 2.0-rc1 compatible with previous versions of OrientDB?

You can open any database created with past versions of OrientDB. In order to use the new binary serialization, you are required to export and re-import the database. For more information, take a look at Migrate from 1.7.x.

Download OrientDB v 2.0-rc1

Have fun with graphs & documents,

Luca Garulli
CEO of Orient Technologies
the Company behind OrientDB
www.orientechnologies.com

The post Released OrientDB 2.0-rc1! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/released-orientdb-2-0-rc1/feed/ 0
OrientDB Academy Launches Free Training! http://www.orientechnologies.com/orientdb-academy-launches-free-training/ http://www.orientechnologies.com/orientdb-academy-launches-free-training/#comments Tue, 16 Dec 2014 12:37:58 +0000 http://www.orientechnologies.com/?p=12227 London, December 16, 2014 It’s been a very productive and exciting final quarter at Orient Technologies. We’re experiencing our most prolific growth to date […]

The post OrientDB Academy Launches Free Training! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, December 16, 2014

It’s been a very productive and exciting final quarter at Orient Technologies. We’re experiencing our most prolific growth to date and are now regularly fielding inquiries from major corporations implementing OrientDB for mission critical production projects.

We have turned the corner: it is evident now that OrientDB is modernizing the database industry.

As you are likely aware, we’re in the final stages of fine-tuning our major 2.0 release of OrientDB! Not only has our development team been hard at work implementing new features, but we’ve also made major improvements to support our active community.

Today we would like to announce the immediate availability of a FREE training series!

FREE OrientDB 2.0 – Getting Started

 

Here at Orient Technologies, we believe the future of data requires a multi-model database due to its infinite power and flexibility. After more than 30 yrs of Relational DBMSs, we understand that it can be challenging at first to use innovative technology like OrientDB. So, we decided to provide a Getting Started video course for FREE!

This course is designed to help developers become productive and familiar with OrientDB and related tools in the fastest way possible. For our initial launch, we have decided to use the Udemy.com platform to provide the most immersive, wide reaching platform possible.

What is included in the course:

• 19 video presentations covering topics ranging from data modeling to hands-on demonstrations of working in OrientDB Studio.

• 19 quizzes to ensure you have galvanized the lessons taught in each section.

• A comprehensive demonstration database and data generation mechanism to put you in front of realistic, highly-connected working data.

Access the FREE OrientDB – Getting Started course.

We can’t express enough our excitement to welcome you into our community! This course will have you up and productive in a matter of days.

Enjoy the course and get involved with our growing community!

Have fun with documents and graphs,

The OrientDB Team

 

The post OrientDB Academy Launches Free Training! appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/orientdb-academy-launches-free-training/feed/ 0
OrientDB Multi-Master Replication on Jelastic http://www.orientechnologies.com/multi-master-replication-jelastic/ http://www.orientechnologies.com/multi-master-replication-jelastic/#comments Sat, 29 Nov 2014 12:41:32 +0000 http://www.orientechnologies.com/?p=12138 Because Jelastic PaaS implements the cartridges packaging model, the list of supported servers has been significantly extended. In addition to the ability to prepare a package with any […]

The post OrientDB Multi-Master Replication on Jelastic appeared first on OrientDB Multi-Model NoSQL Database.

]]>
Because Jelastic PaaS implements the cartridges packaging model, the list of supported servers has been significantly extended. In addition to the ability to prepare a package with any desired stack (either based on the already existing OpenShift’s one or one originally created by yourself), there are a number of ready-to-use cartridge templates available within our Templates repository. They can be easily installed to the Jelastic Cloud by an administrator, and OrientDB is one of these.

OrientDB is the first multi-model open-source NoSQL distributed database system, which combines the power of graphs and the flexibility of documents in one scalable and high-performance operational solution. Working with OrientDB, you receive the numerous features and possibilities due to its integrated blend of graphs relational behaviour and document-type storage. And in order to benefit even more, you are able to gain the improved reliability of your data due to its Multi-Master replication support.

It’s well known that replication is a basic security solution for any database server, aimed to increase its failover capabilities. With OrientDB, you can easily create a secure cluster with several replicated database servers in it and, in such a way, reduce the risks of downtime or data loss, increase accessibility, get a high level of performance and product confidence.

In this instruction, we’ll show you how to configure the replication between two OrientDB servers, where all of the records inside the same-named databases are replicated. However, your DB cluster may include any desired amount of nodes – just adjust every one of them based on the steps below (as Multi-Master replication mode means that all servers in a cluster are equal and able to write/read records of each other).

So, let’s get started!

Create an Environment

1. Log in to your Jelastic account and Create a new environment with the corresponding button at the top left corner of your dashboard.

create environment

2. You’ll see the topology dialog window opened. Disable the automatically added application server (as you won’t need it for this tutorial) and pick the OrientDB server instead.

Note: OrientDB is an optional node since it is based on cartridge packaging model. If you can’t find this server in the NoSQLsection of your wizard, send a request to your hosting provider for its addition.

Increase the amount of OrientDB nodes using the + button in the central Horizontal scaling pane. Then, state the resource usage limits for this server with the help of cloudlet sliders, specify the desired environment name (for example, orientdb), and click Create to continue.

orientdb multi nodes

3. Once your environment is successfully created and has appeared at your dashboard, you can proceed to the next chapter of this guide.

orientdb hosting

Database Configuration

Now let’s configure each of the nodes in your cluster in order to set up a replication between them.

1. Click the Config button for your database server.

config orientdb

2. In the appeared Configuration Manager tab, navigate to the hazelcast.xml file within the conf/config directory and edit the code in its group and network sections in the following way:

<group>
    <name>{custom_name}</name>
    <password>{custom_password}</password>
</group>
<network>
    <port auto-increment=”false“>{port}</port>
    <join>
        <multicast enabled=”false“>
            <multicast-group>235.1.1.1</multicast-group>
            <multicast-port>2434</multicast-port>
        </multicast>
    </join>
</network>

Note that you should substitute the values in the curly brackets with your data:

    • {custom_name} – an arbitrary name for your replication group (must be the same for every node, e.g. root)
    • {custom_password} – the desired password for your replication group (must be the same for every node, e.g.abc123)
    • {port} – any unoccupied port (e.g. 3000)

hazelcast orientdb

3. Then, add the tcp-ip code subsection to the same file just after the closing multicast tag inside the join section.

<tcp-ip enabled=”true”>
<member>
{node_ip}:{port}</member>
<member>
{node_ip}:{port}</member>
</tcp-ip>  

where:

  • {node_ip} – IP addresses of the included to cluster nodes, which you would like the replication to be configured for
  • {port} – port number, the same as you’ve specified for the auto-increment parameter in the previous step (3000 in our case)
Note: The required IP addresses can be found by means of selecting the gear icon next to each of your database nodes.
database ip

orientdb tcp ip

4. In order to save your time and not repeat the same operations for every node, use the Save for all instances option from the Save drop-down list above the editor.

save configs orient

In such a way, the performed configuration changes will be applied to all the nodes in your DB cluster.

5. After that, switch to the default-distributed-db-config.json file, located in the same folder, and set the preferred names (e.g. nodeN) for all of your replicated nodes within the servers parameter, substituting the default <NEW_NODE> string.

Take into consideration the required value format: entered names should be enclosed in quotation marks and separated with comma.

“servers” : [ “node1″, “node2″ ]

orientdb servers

6. Save for all instances one more time and switch to the orientdb-dserver-config.xml file still in the conf/config directory.

Pay attention to the exact name of the required configuration file (as the current folder contains the similar one) – it should include the dserver word.

Find the HTTP protocol setting in the <listeners> file section (approximately at the 73d code line) and edit the port-rangevariable value, stating it to 8080-8090.

orientdb listener

Save the changes for all nodes in the way you’ve done it recently.

7. In order to protect your database servers from the unauthorized access, let’s set the admin username and password for them.

Note: This step is optional, but highly recommended.

You can copy and use the default credentials from the orientdb-server-config.xml file (they were also sent to you via email after environment creation) or add your own, new ones. We’ll use the custom root/qwerty credentials as an example. So, specify the desired values within the following line:

<user name=”root” password=”qwerty” resources=”*”/>

Then, in the same file, scroll a bit down (approximately to the 100th line) and paste the received string inside the users section.

credentials orient

Depending on your preferences, the credentials could be identical (in this case use the Save for all instances option at any node you’ve performed the changes for) or different for each of your nodes (use Save only for the current instance for applying the changes at every instance).

8. Once all the required changes are saved, navigate to the beginning of the same file and uncomment the first nodeNameparameter in the <handler class=”com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin”> section.

This time you need to make the different changes for each node, modifying this parameter by means of entering the stated (in the 4th step) node names, inside the value variable. In accordance with the earlier specified settings in this instruction, the values should be:

  • for the first node:
    <parameter name=”nodeName” value=”node1″/>
  • for the second node:
    <parameter name=”nodeName” value=”node2″/>

You can switch between the nodes via the appropriate list in the top left part of the Configuration Manager tab (circled at the image below).

orientdb instance

Do not forget to save the changes separately, with the help of Save only for the current instance option instead of the previously used Save for all instances one.

7. Finally, find the server.sh script inside the bin directory, and change the default configuration file, used by your DB server, to orientdb-dserver-config.xml within the CONFIG_FILE variable.

orientdb replication

Note: If you can’t find the mentioned folder in your Configuration Manager, please send a request to your hosting provider for OrientDB cartridge re-importing in order to get all the new functionality available.

Save new settings for all instances.

8. In order to run your cluster with all the new configurations applied, you need to Stop your environment and Start it again using the appropriate buttons next to it.

start orientdb

Replication Check Up

As soon as your servers are running, let’s check the data is replicated inside the set of your nodes. For that we’ll create the same-named DB at each of the instances and ensure that classes and records inside it are instantly copied to all nodes after the addition.

1. Open the first database node in browser in order to access its OrientDB Studio administration panel.

access orientdb

2. Enter your admin credentials (if you set them) in the appeared pop-up window and click the Create new database button.

create database orient

3. In the opened dialog frame, type the desired database name (e.g. jelastic) and specify your admin credentials. Optionally, select the preferred Type and Storage Type within the corresponding drop-down lists and click on Create database to finish.

orientdb new database

4. Repeat the first three steps for the rest of your DB servers in order to create a compound of the databases with the same name inside your cluster.

Note: that it’s an obligatory operation for the proper replication work; once created at a single node, the database won’t appear at others without restarting your environment.

database orient

5. After that, Connect to this newly created database at the random OrientDB instance by choosing it from the Database drop-down list and specifying your admin credentials (if there are any).

connect to db orient

6. Once inside, switch to the Schema tab and click on the New Class button.

orientdb schema

7. In the shown pop-up window, type the name of your new class (e.g. Repl-test) and define the remained options if necessary (or leave them blank). Click Save to finish.

new class orientdb

8. Now, let’s add a simple record to our class (click on the New Record button next to it).

orientdb add record

9. We’ll adjust this record to contain the additional custom field. You can add it through choosing the Add field option within the Actions list.

add fiels orientdb

Specify the desired field name (for instance, Name), set the string type for it and click Add field to proceed.

field string orient

10. Now, let’s set any name for our new record, e.g. John. Save the changes with the corresponding button.

create record orient database

11. Finally, connect to the same jelastic database at all the rest OrientDB nodes and check that the Repl-test class with your custom record exists at every one of them.

jelastic orient databasemulti master replica orient

Great! As you can see, replication works like a charm, so you can start using your DB cluster according to your needs without worrying about the data’s safety.

Register for a free 2-week trial now and check it out yourself!

 

The post OrientDB Multi-Master Replication on Jelastic appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/multi-master-replication-jelastic/feed/ 0
Released OrientDB 2.0-M3 http://www.orientechnologies.com/released-orientdb-2-0-m3/ http://www.orientechnologies.com/released-orientdb-2-0-m3/#comments Tue, 18 Nov 2014 19:27:46 +0000 http://www.orientechnologies.com/?p=12068 London, November 18, 2014 Orient Technologies released OrientDB 2.0-M3. This is last Milestone before the 2.0-final. We fixed many issues reported in M2 and […]

The post Released OrientDB 2.0-M3 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, November 18, 2014

Orient Technologies released OrientDB 2.0-M3. This is last Milestone before the 2.0-final. We fixed many issues reported in M2 and we supported some new features we are sure you’ll appreciate: 115 issues in total. Please help us to test OrientDB 2.0-M3 so that we can release a stable final 2.0 in few days.

- Core: 
  - Cluster selection strategy now can decide on the input document content
  - Better automatic alloc of Heap and Disk-Cache
  - Clusters can be detached (offline) and re-attached (online)
  - FetchPlan: support for wildcards
  - Improved pools
  - Using SIGTRAP (kill -5) to dump OrientDB information
  - Fixed connection pool problem on high usage
  - Cache is always ON and can’t be disabled anymore. This avoids many common
    issues with users
- Schema: used immutable instances to reduce locking contention
- Graph API:
  - New OGraphBatchInsertBasic and OGraphBatchInsert API for massive insertion on graphs:
  - 13x faster than Blueprints
- Document API: Removed a couple of internal layers to speedup and simplify implementation
- Studio: Simplified database creation (graph - no lightweight edges by default)
- Console: Displayed also @class
- Bug fixing: 115 total issues from 2.0-M2.

 

Full list: https://github.com/orientechnologies/orientdb/issues?q=milestone%3A2.0-M3+is%3Aclosed.

 

Can I use OrientDB v2.0-M3 in production?

No. This is not the final 2.0 version. This release is the third milestone (M3 stands for Third Milestone) of 2.0 on the path to the final version in the next days. We suggest using OrientDB v2.0-M3 in development and test only. If you plan to go in production before December, we suggest staying with OrientDB 1.7.x. Otherwise, go ahead and use OrientDB 2.0-M3.

 

Is 2.0-M3 compatible with previous versions of OrientDB?

You can open any database created with past versions of OrientDB. In order to use the new binary serialization, you are required to export and re-import the database. For more information, take a look at Migrate from 1.7.x.

Download OrientDB v 2.0-M3

Have fun with graphs & documents,

Luca Garulli
CEO of Orient Technologies
the Company behind OrientDB
www.orientechnologies.com

 

The post Released OrientDB 2.0-M3 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/released-orientdb-2-0-m3/feed/ 0
What about the Gartner Magic Quadrant 2014? http://www.orientechnologies.com/what-about-gartner-mq/ http://www.orientechnologies.com/what-about-gartner-mq/#comments Fri, 24 Oct 2014 17:38:54 +0000 http://www.orientechnologies.com/?p=11973 What about the Gartner Magic Quadrant 2014?   As you may know, OrientDB was the first native graph database to be included on the […]

The post What about the Gartner Magic Quadrant 2014? appeared first on OrientDB Multi-Model NoSQL Database.

]]>
What about the Gartner Magic Quadrant 2014?

 

As you may know, OrientDB was the first native graph database to be included on the “Operational DBMS” Magic Quadrant published by Gartner in 2013. We are very proud of this accomplishment. We knew some time back that we would not be included on the 2014 edition, as new restrictions pertaining to commercial paid customers and overall company revenue were introduced. OrientDB’s roots are in free and open source software. Many of our users are unknown to us and utilize our database free of charge.

First, our status change has nothing to do with product performance or customer concerns. Essentially, we narrowly missed the revenue and paying customer requirements. While we were disappointed to see the restrictions exclude OrientDB, we are on track with our corporate goals and will continue to move forward with our strategy as planned.

Consider these new features introduced since the 2013 Magic Quadrant report:

  • Multi-master replication in synchronous and asynchronous modes. Auto discovery and High Availability
  • Support for SSL connections
  • New Off-Heap In-Memory only database
  • Distributed Sharding for Big Data
  • A full Enterprise Workbench tool providing advanced analytics, query metrics and clustered deployment management
  • A game changing Studio with best in class graph visualization and modification tools
  • 300% increased performance on replication
  • Graph Refactoring facilities for moving vertices to a new class, cluster or server node while preserving all the links
  • New binary format improving speed and reducing disk usage
  • Improved support for Multi-Core architecture
  • Ability to put clusters temporarily offline to park historical data
  • SQL statistics functions, Parallel Queries, Full-Text and Geo Spatial indexes and much more…

 

This is just the tip of the iceberg. As a company, we are seeing tremendous momentum. Just within the last quarter, we have won major engagements with 2 of America’s Fortune 5 companies. This coupled with several projects at other prominent tech companies proves without a doubt that 2015 will be a big year for us.

So what does this all mean? It means we’re on track and in tune with our core strategies. We started with a focus on the product. Quality and capability are our first and foremost objectives. Next, we coupled our product with a permissive Apache 2 license. The third phase is just now taking off. This is offering world class services to those customers who wish to engage Orient Technologies.

Keep an eye on us. There are big things happening under the covers. Our professional services branch is growing rapidly with qualified partners worldwide, extended coverage, on site/remote consulting services and improved support service level agreements.

Our professional services are in high demand and will easily bring us to the minimum threshold for the next year. From a product perspective, when it comes to an “operational graph database” just compare the features and you’ll quickly realize there just isn’t another option like OrientDB.

Best wishes,
The team at Orient Technologies

 

The post What about the Gartner Magic Quadrant 2014? appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://www.orientechnologies.com/what-about-gartner-mq/feed/ 0