OrientDB Multi-Model NoSQL Database http://orientdb.com OrientDB is a Multi-Model NoSQL Database with Graph and Document engine Thu, 04 Feb 2016 18:02:57 +0000 en-US hourly 1 Released OrientDB 2.1.10 http://orientdb.com/released-orientdb-2-1-10/ http://orientdb.com/released-orientdb-2-1-10/#comments Thu, 04 Feb 2016 18:02:57 +0000 http://orientdb.com/?p=13306 London, February 4, 2016 The OrientDB Team has just released OrientDB v2.1.10, resolving 25 issues from v2.1.9. This is the last stable release. Please […]

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

]]>
London, February 4, 2016

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

Download OrientDB v2.1.10 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.10 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/released-orientdb-2-1-10/feed/ 0
OrientDB Experiences Record Growth in 2015. Momentum Paves Way For Transformative 2016 http://orientdb.com/orientdb-experiences-record-growth/ http://orientdb.com/orientdb-experiences-record-growth/#comments Tue, 02 Feb 2016 15:46:58 +0000 http://orientdb.com/?p=13246 OrientDB Takes Off in 2015 and Announces Remarkable Growth   Key highlights include senior management hires, community awards, coverage by leading analysts, record subscription […]

The post OrientDB Experiences Record Growth in 2015. Momentum Paves Way For Transformative 2016 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
OrientDB Takes Off in 2015 and Announces Remarkable Growth

 

Key highlights include senior management hires, community awards, coverage by leading analysts, record subscription growth and breakthrough product innovation

London, UK (February 2, 2016) – OrientDB Ltd, the company behind the first-ever distributed multi-model database, announces a year of record growth that paves the way for a transformative 2016.

Leading analysts continue to highlight the surge of multi-model databases and the tremendous opportunity for customers to accelerate the pace of innovation by using a few operational databases rather than many different technologies. Natively supporting graphs, documents and the familiar SQL dialect, OrientDB is a general-purpose solution to naturally process today’s data which is generated at unbelievable speed. That opens the doors to a new class of applications, drastically reduces the costs and removes the need to keep multiple DBMSes aligned.

“With the release of OrientDB 2.1 and breakthrough innovation coming in OrientDB 2.2, we are making the industry’s first distributed document-graph database even better.” said Luca Garulli, CEO and Founder. “When I started to work on OrientDB back in 2010, I could only imagine the pace of growth we’re seeing today thanks to our customers, users and advocates.”

Product and Ecosystem Milestones

 

“The multi-model market started to blossom in 2015 as enterprises shift towards a simplified architecture that marries connected, unstructured and structured data processed at a speed never possible before,” said Luca Olivari, President. “OrientDB pioneered the multi-model approach and is best positioned to capitalize on this massive change.”

Company Momentum

About OrientDB

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. The native multi-model database combines the connectedness of graphs, the agility of documents and the familiar SQL dialect. Fortune 500 companies, government entities and startups all use the technology to build large-scale innovative applications. Some of their clients include Ericsson, the United Nations, Pitney Bowes, Sky, CenturyLink and Sonatype. OrientDB recently won the prestigious 2015 Infoworld Bossie award.

Resources:

 

The post OrientDB Experiences Record Growth in 2015. Momentum Paves Way For Transformative 2016 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/orientdb-experiences-record-growth/feed/ 0
OrientDB – Sequence (embedded) by Matan Shukry http://orientdb.com/orientdb-sequence-by-matan-shukry/ http://orientdb.com/orientdb-sequence-by-matan-shukry/#comments Wed, 20 Jan 2016 11:07:18 +0000 http://orientdb.com/?p=13214 This is a guest post by OrientDB contributor Matan Shukry. Hi, My name is Matan Shukry, and I’m a Programmer, DBA, and a Big […]

The post OrientDB – Sequence (embedded) by Matan Shukry appeared first on OrientDB Multi-Model NoSQL Database.

]]>
This is a guest post by OrientDB contributor Matan Shukry.

Hi,

My name is Matan Shukry, and I’m a Programmer, DBA, and a Big Data engineer.

Today I’ll talk about my contribution to OrientDB, with emphasis on sequences.

The concept of sequences should be familiar to most people who used an RDBMS before. However, for those of you who aren’t familiar with it, I’ll give a short description on the topic.

Sequence is a database object that generates numbers sequentially. It is mostly used for automatically incremented columns.

Sounds simple, right? Well, here comes the tricky part:

    1. Sequences do not necessarily generate numbers in an ordered fashion. Assuming A and B are retrieve operations, where B happens after A, A may result in a number that is higher than B.
    2. Sequences do not necessarily generate numbers in a continuous fashion. Assuming A and B are retrieve operations, where B happens after A, the difference between the result of B and A may be bigger than 1. That is, there may be “holes” between sequence values.

 

Both of the above points happen due to a caching mechanism, where a range of numbers are kept in memory, and when requested are provided to the user. However, in some cases such as a transaction rollback or a server shutdown, the numbers are lost. Furthermore, in many cases there is also an option in the sequence to turn off caching in order to provide a sequence that generates ordered and continuous numbers.

Starting from version 2.2, a sequence object has been introduced to OrientDB. It contains two types (ordered and cached), and include ‘start’ and ‘increment’ fields.

The sequence object in OrientDB uses optimistic transaction (MVCC). When the sequence needs to allocate more numbers (either a range of them with cached sequence or a single one with ordered sequence), it will retrieve the document, change it’s properties, and attempt to save it (commit). If the sequence document is too old, meaning another connection changed the document and committed it in between our retrieve-and-save, the sequence will attempt to retry the operation again. If the operation fails a certain number of retries, an exception is thrown back to the user, after which the user decides what to do next. The entire process happens at the database layer, and it’s very quickly.

Also, an automatically-increment column type (which will rely on the sequence object, together with the default value feature) will probably be added in the near/distant future. As you probably figured out by now, this will result in inserting an automatically-incremented number into a specific column. 

Here are a few examples on how to use sequences. Consider a blog site where we would like each post to have a unique id. We would create the sequence as follows:

SQL

CREATE SEQUENCE postId TYPE CACHED START 101 INCREMENT 2 CACHE 20

Java

OSequence seq = database.getMetadata().getSequenceLibrary().createSequence(“postId”, OSequence.SEQUENCE_TYPE.CACHED, new OSequence.CreateParams().setStart(101).setIncrement(2).setCacheSize(20));

Each time we’ll want to insert a new post, we’ll use .next():

SQL

INSERT INTO Post SET id = sequence(“postId”).next(), title=”BTE - Best Title Ever”, body=”…”

Java (Graph API)

OSequence seq = graphDB.getRawGraph().getMetadata().getSequenceLibrary().getSequence(“postId”);
graphDB.addVertex(“class:Post”,
“id”, seq.next(), “title”, “BTE - Best Title Ever”, “body”, “…”);

Java (Document API)

OSequence seq = database.getMetadata().getSequenceLibrary().getSequence(“postId”); 
ODocument doc = new ODocument(“Post”); 
doc.fields(“id”, seq.next(), “title”, “BTE – Best Title Ever”, “body”, “…”); 
doc.save();

 

You can also change the sequence parameters (alter): 

SQL

ALTER SEQUENCE postId START 1001 INCREMENT 30 CACHE 40

Java

database.getMetadata().getSequenceLibrary().getSequence(“postId”).updateParams(new OSequence.CreateParams().setStart(1001).setIncrement(30).setCache(40));

 

If at some point we would like to retrieve the current value without incrementing it or reset it back to 0 (probably when playing around in your development environment):

SQL

SELECT sequence(“userId”).current()
SELECT sequence(“userId”).reset()

Java

OSequence seq = database.getMetadata().getSequenceLibrary().getSequence(“postId”); 
long value = seq.current(); 
seq.reset();

P.S.

There is a workaround in order to create an auto-increment fields in previous versions of OrientDB (<v2.2). Check out this page for more information.

 

Hope this comes in handy,

Matan Shukry
 _

The post OrientDB – Sequence (embedded) by Matan Shukry appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/orientdb-sequence-by-matan-shukry/feed/ 0
Released OrientDB v2.1.7 with new configurable graph consistency http://orientdb.com/released-orientdb-v2-1-7/ http://orientdb.com/released-orientdb-v2-1-7/#comments Wed, 09 Dec 2015 13:03:40 +0000 http://orientdb.com/?p=13136 London, December 8, 2015 The OrientDB Team has just released OrientDB v2.1.7, resolving 18 issues from v2.1.6. This is the last stable release. Please […]

The post Released OrientDB v2.1.7 with new configurable graph consistency appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, December 8, 2015

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

This release introduced also the new configurable Graph Consistency to speedup change operations against graphs. For more information look at Graph Consistency.

Download OrientDB v2.1.7 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,

Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB

The post Released OrientDB v2.1.7 with new configurable graph consistency appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/released-orientdb-v2-1-7/feed/ 0
Released OrientDB v2.1.6 http://orientdb.com/released-orientdb-v2-1-6/ http://orientdb.com/released-orientdb-v2-1-6/#comments Tue, 24 Nov 2015 02:36:21 +0000 http://orientdb.com/?p=13115 London, November 23, 2015 The OrientDB Team has just released OrientDB v2.1.6, resolving 38 issues from v2.1.5. This is the last stable release. Please upgrade your […]

The post Released OrientDB v2.1.6 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
London, November 23, 2015

The OrientDB Team has just released OrientDB v2.1.6, resolving 38 issues from v2.1.5. This is the last stable release. Please upgrade your production environments to v2.1.6. This release also resolved all known issues related to the distributed architecture. For more information, take a look at the Change Log.

NOTE: Starting from v2.1.6 it’s not possible an hot upgrade of a running cluster of OrientDB nodes (upgrading nodes one by one), because the usage of the last version of Hazelcast that breaks such network compatibility. If you’re upgrading a distributed architecture you should power off the entire cluster and restart it with the new release.

Download it 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,

Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB

 

The post Released OrientDB v2.1.6 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/released-orientdb-v2-1-6/feed/ 0
Cambridge Intelligence and OrientDB Announce New Graph Partnership
 http://orientdb.com/cambridge-intelligence-and-orientdb-announce-new-graph-partnership%e2%80%a8/ http://orientdb.com/cambridge-intelligence-and-orientdb-announce-new-graph-partnership%e2%80%a8/#comments Wed, 11 Nov 2015 13:00:33 +0000 http://orientdb.com/?p=12985 CAMBRIDGE, UK and London, UK – 11 November 2015, Cambridge Intelligence, creators of the KeyLines network visualization toolkit and OrientDB, Ltd the sponsor of OrientDB, […]

The post Cambridge Intelligence and OrientDB Announce New Graph Partnership
 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
CAMBRIDGE, UK and London, UK – 11 November 2015, Cambridge Intelligence, creators of the KeyLines network visualization toolkit and OrientDB, Ltd the sponsor of OrientDB, the pioneering multi-model DBMS, today announced a new partnership.

The partnership between the firms will pave the way for new integrated customer solutions built with both technologies. Using the KeyLines visualization technology, OrientDB users will be able to easily integrate intuitive and powerful visual data exploration and analysis capability into their existing big data solutions.

“The combination of KeyLines and OrientDB is an exciting new opportunity,” said Joe Parry, CEO of Cambridge Intelligence.

“Cambridge Intelligence and OrientDB are a great fit for one another, offering complimentary expertise and technologies that are in real demand.  We look forward to working closely together to help customers build the solutions they need to make sense of their complex connected data.”

OrientDB has enjoyed rapid adoption in the NoSQL market, with organizations keen to benefit from its ‘hybrid’ approach to data storage, combining the flexibility of a document store with the connectedness of a graph database.

“Storing and visualizing complex relationships is fundamental to easily explore data and uncover hidden patterns,” said Luca Olivari, President of OrientDB. “Keylines and OrientDB can provide unique insights to customers on a journey to better leverage connected data and gain competitive advantage.”

The combination of KeyLines and OrientDB will generate significant operational benefits and data insight in a number of different use cases, including cyber security, anti-fraud and data discovery.

To know more about the partnership please register to the upcoming webinar Maximizing OrientDB Data Insight with Visualization.

About Cambridge Intelligence

Cambridge Intelligence Limited is a leading provider of visualization and analysis solutions, designed to help organizations understand their complex connected data. By combining award-winning software, unrivalled know-how and expert developer services, the company aims to make network visualization accessible and meaningful across many industries.

About OrientDB Ltd

OrientDB Ltd is a private company that officially leads the development of the OrientDB Open Source Project. OrientDB is a 2nd Generation Distributed Graph Database with the flexibility of Documents in one product with an Open Source commercial friendly license. First generation Graph Databases lack the features that Big Data demands: multi-master replication, sharding and more flexibility for modern complex use cases.

The post Cambridge Intelligence and OrientDB Announce New Graph Partnership
 appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/cambridge-intelligence-and-orientdb-announce-new-graph-partnership%e2%80%a8/feed/ 0
OrientDB (more than) SQL http://orientdb.com/orientdb-more-than-sql/ http://orientdb.com/orientdb-more-than-sql/#comments Fri, 06 Nov 2015 11:02:16 +0000 http://orientdb.com/?p=13049 Author: Luigi Dell’Aquila  – @ldellaquila Do you know SQL? If you’re a software developer/DBA/DevOps, I’m pretty certain that I know your answer to that question. […]

The post OrientDB (more than) SQL appeared first on OrientDB Multi-Model NoSQL Database.

]]>
Author: Luigi Dell’Aquila  – @ldellaquila

Do you know SQL? If you’re a software developer/DBA/DevOps, I’m pretty certain that I know your answer to that question.

This is precisely why OrientDB adopted SQL as its main query language.

SQL is elegant, clear, well-defined, and powerful (for what concerns RDBMS), but it was created during a period when tables were the only allowed data structure (you know, relational databases, tables, primary keys, foreign keys…)

Now, with NoSQL, things have changed. Data structures are now much more complex, so  SQL requires some enrichments to fit this new model.

Let’s see how OrientDB SQL is similar to the standard SQL and how it differs.

The past: Join, Filtering, Projection, Aggregation

This is how standard SQL works in relational databases.

Let’s take a look with an example: calculate the population of all European countries (that is the sum of all the populations of its cities).

City:

name countryId population
Rome 32 2.500.000

 

Country

id name
32 Italy

 

SELECT country.name, sum(city.population)
FROM city, country 
WHERE city.countryId = country.id
AND country.continent = ‘Europe’
GROUP BY country.name

 

You can think at the execution of this query in four steps:

  1. Join: match city and country tables based on a primary key (country.id) and a foreign key (city.countryId)
  2. Filtering: filter results based on some attributes (the continent name in this case)
  3. Projection: choose a subset of attributes to be returned (country name and city population in this case)
  4. Aggregation: aggregate data, calculate the sum of populations grouping by country name


This is a typical pattern in SQL, but it has some problems:

Problem 1: the Join operation is EXPENSIVE, it relies on a convention (the same value on country.id and city.countryId) and it has to be re-calculated at every query execution.

The situation is even more critical when you have MULTIPLE joins. Let’s make it more complicated:

SELECT country.name, sum(city.population)
FROM city, region, state, country, continent
WHERE city.regionId = regiony.id
AND region.stateId = state.id
AND state.countryId = country.id
AND country.continentId = continent.id
AND continent.name = ‘Europe’
GROUP BY country.name

 

How much time will it take to execute?

Problem 2: We are assuming that we know how deep the hierarchy is, but in some cases, we simply don’t know. Suppose you are dealing with an organization structure, with departments, managers and so on, how can you write a query that returns all the sub-trees under a manager?

Problem 3: Until now, we just assumed that our data is made of simple attributes, eg. the country name is a string, the city population is an integer. But this does not represent reality very well.

An example could be having a list of names for the same city.

names countryId population
[Rome, Roma] 32 2.500.000

Or even better, a list of names with languages 

names countryId population
[  {name: Rome, language: EN},   {name: Roma, language: IT} ] 32 2.500.000

It is not possible in standard RDBMS (but it is in NoSQL), so regular SQL lacks the commands to manage this kind of data. 

Problem 4: The schema is well-defined here, so we know exactly which properties a single table has and SQL was designed to work on this assumption. It’s not true in NoSQL, so we will need some extensions to manage cases where we don’t know the schema (or where there is no defined schema at all).

From Join to links

A Join operation is expensive, so OrientDB replaced it with something better: physical links

City:
{
   @rid: #11:50,
   name: “Rome”,
   population: 2.500.000,
   country: #12:32
}

Country:
{
   @rid: #12:32,
   name: “Italy”
}

 

The big difference here is that @rid values are not a convention, they just represent a physical position of a record, so calculating a relationship is a very fast operation, O(1) while the cost of a single lookup for a primary key in an RDBMS is O(logN).

Efficiency is a big advantage, of course, but SQL has to be enhanced to leverage this new element.

In OrientDB SQL, a join is not allowed, so relationships are calculated using dot notation:

Relational OrientDB (Document)
SELECT country.name, sum(city.population) 
FROM city, country 
WHERE city.countryId = country.id 
AND country.continent = ‘Europe’
GROUP BY country.name
SELECT country.name, sum(population)
FROM city
WHERE country.continent = ‘Europe’
GROUP BY country.name
SELECT country.name, sum(city.population) 
FROM city, region, state, country, continent
WHERE city.regionId = regiony.id
AND region.stateId = state.id
AND state.countryId = country.id
AND country.continentId = continent.id
AND continent.name = ‘Europe’
GROUP BY country.name
SELECT region.state.country.name as contryName, sum(population)
FROM city 
WHERE region.state.country.continent.name = ‘Europe’
GROUP BY countryName

 

From Links to Edges

OrientDB is also a Graph Database, so you can also represent your data elements as Vertices and relationships as Edges.

The big difference is that Edges are bidirectional, which means you can traverse them in both directions with the same efficiency, using out() and in() operators for outgoing and incoming edges.

Eg.

sql-img1

you can retrieve the continent of a city with:

SELECT out(‘inRegion).out(‘inState’).out(‘inCountry).out(‘inContinent’)
FROM city 
WHERE name = ‘Rome’

 

but you can also retrieve all the cities in a continent:

SELECT in(‘inContinent’).in(‘inContry’).in(‘inState’).in(‘inRegion’)
FROM continent 
WHERE name = ‘Europe’

 

Deep traversal

Sometimes you know how deep you have to traverse (eg. city -> region -> state -> country), but in other cases, you just don’t know. Consider having an organization structure:

sql-img2

If you want to retrieve all of the subtrees of a given department, but you don’t know how deep the structure is, there is no way to write a single standard SQL statement to perform the job.

OrientDB SQL has an extension called TRAVERSE, specifically designed for this use case

The following statement retrieves all the sub-departments of Dept 1

TRAVERSE in(‘Parent’) from (
    SELECT * FROM Department WHERE name = ‘Dept 1’
)

 

The following one retrieves the first three levels of sub-departments of Dept 1:

TRAVERSE in(‘Parent’) from (
    SELECT * FROM Department WHERE name = ‘Dept 1’
) WHILE $depth <= 3

 

or just, using the new MAXDEPTH operator:

TRAVERSE in(‘Parent’) from (
    SELECT * FROM Department WHERE name = ‘Dept 1’
) MAXDEPTH 3

 

You can also filter the result of this traversal to retrieve only the third level:

SELECT * FROM (
    TRAVERSE in(‘Parent’) from (
       SELECT * FROM Department WHERE name = ‘Dept 1’
   ) WHILE $depth <= 3
) WHERE $depth = 3

 

The WHILE condition is used by the query to decide if the traversal has to continue on the current traversal branch. It can contain any boolean expression that could be evaluated in a WHERE condition.

Dealing with complex types

Standard SQL was designed to manage simple data types (eg. strings and numbers). OrientDB data model is quite complex compared to RDBMS: records can have simple attributes (strings, numbers, dates), link attributes (see dot notation), list and set attributes, embedded objects. As a consequence, OrientDB SQL was enriched to manage this kind of data.

Managing collections and embedded objects

Records can be created with complex attributes, eg.

INSERT INTO Conference SET
name = ‘OrientDB Next World Conference’, 
tags = [‘NoSQL’, ‘Graph’, ‘Document’], 
location = {address: ‘abc Street’, city: {name: ‘London’, country: {name: ‘UK’}} }

 

sql-img3

The result will be the following:

{
   @class: Conference,
   @rid: #12:10, //self generated and managed by OrientDB
   name:  ‘OrientDB Next World Conference’,
   tags = [‘NoSQL’, ‘Graph’, ‘Document’], 
   location = {
      address: ‘abc Street’, 
      city: {
         name: ‘London’, 
         country: {
            name: ’UK’
         }
      } 
   }
}

 

As you can see, complex attributes are not managed as strings or BLOBs: they are first-class, structured objects that can be queried and manipulated via SQL.

To add a new tag to the conference, we can just use the UPDATE ADD syntax:

UPDATE Conference ADD tags = ‘Multi-Model’ 
WHERE name = ‘OrientDB Next World Conference’

 

To remove a tag, you can just use UPDATE REMOVE syntax:

UPDATE Conference REMOVE tags = ‘NoSQL’ 
WHERE name = ‘OrientDB Next World Conference’

 

You can also use DOT notation to update embedded objects content, eg.

UPDATE Conference SET location.city.country.name = ‘United Kingdom’ 
WHERE name = ‘OrientDB Next World Conference’

 

Querying the Conference class will result in a single record:

sql-img4

 

UNWINDing collections

In some cases, you will need to unwind collection attributes to have a single row per collection item.

OrientDB 2.1 provides a new UNWIND operator, specifically designed for this need:

SELECT FROM Conference UNWIND tags

sql-img5

UNWIND operator can also be used to unwind multiple collections in the same query.

Querying collections and embedded objects

Of course, you will be able to compare collections with other collections using a WHERE condition.

SELECT FROM Conference WHERE tags = [‘Graph’, ‘Document’, ‘Multi-Model’]

 

but in some cases, you will have to query for collections that contain a particular value:

SELECT FROM Conference WHERE tags contains ‘Graph’

 

or for embedded objects that contain a particular value as a key or as a value:

SELECT FROM Conference WHERE location containsKey 'address'

 

SELECT FROM Conference WHERE location containsValue 'abc Street'

Working with Schema(less)

OrientDB allows you to work with a dynamic schema or in a completely schemaless mode, which means that two records in the same class can have completely different attribute sets and types.

OrientDB is very tolerant when dealing with non-existing attributes, eg. queries will never result in an error if attributes in the WHERE condition are not defined for a particular record.

Sometimes you just want to query a set of records based on their content, without having all the complete information about their schema. Consider querying the Conference class for any records that contain the word ‘OrientDB’ in any of their attributes, you can use any() operator for this:

SELECT FROM Conference WHERE any() like ‘%OrientDB%’

 

Of course, if needed, you can define a strict schema for your classes, so you can define attribute names, types, and constraints (not null, min, max etc.)

sql-img6

When you have a defined schema, you can query it using SQL:

SELECT expand(classes) from metadata:schema

sql-img7

Conclusion

SQL is a fantastic language because it’s clear and effective, but to harness all the power of a Multi-Model database, it needs some small improvements. OrientDB SQL is very similar to the standard, but includes the addition of operators to operate graph traversal, manage and query complex attributes, and to manage schema and schema-less documents.

If you already know SQL, you are already at 70% of the learning curve and the remaining 30% will be very smooth. All you need to do is get used to a richer, more powerful, versatile and more efficient data model: the Multi-Model database.

 

The post OrientDB (more than) SQL appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/orientdb-more-than-sql/feed/ 0
OrientDB Hires MongoDB and MarkLogic Executive as VP of Sales http://orientdb.com/orientdb-hires-mongodb-and-marklogic-executive-as-vp-of-sales/ http://orientdb.com/orientdb-hires-mongodb-and-marklogic-executive-as-vp-of-sales/#comments Mon, 02 Nov 2015 15:00:24 +0000 http://orientdb.com/?p=12989 Jim Stock Joins OrientDB to Lead and Build the Worldwide Sales Organization London, UK (Nov 2, 2015) – Orient Technologies, the company behind OrientDB […]

The post OrientDB Hires MongoDB and MarkLogic Executive as VP of Sales appeared first on OrientDB Multi-Model NoSQL Database.

]]>
Jim Stock Joins OrientDB to Lead and Build the Worldwide Sales Organization

London, UK (Nov 2, 2015) – Orient Technologies, the company behind OrientDB (www.orientdb.com), the graph-document database that pioneered the multi-model concept, announced today that Jim Stock, an experienced executive in the NoSQL database market, will join the company as Vice President of Worldwide Sales.

Jim is an accomplished enterprise sales leader who brings more than 20 years of experience to Orient Technologies. Most recently, he was Senior Director at MongoDB where he led the EMEA Field Sales team during a time of unprecedented growth. Prior to that, Jim served as a Director at Marklogic where he held a variety of management roles, including running the team responsible for the largest vertical market, Media. Prior to MarkLogic, he spent 9 years in various management positions at Bertelsmann. Throughout his career, Jim has built high performance sales teams that consistently deliver strong results.

“Hiring a sales leader of Jim’s experience is an endorsement of the immense opportunity for the leading multi-model database to transform one of the largest industries,” said Luca Olivari, President, OrientDB. “Jim’s experience with managing enterprise clients and deep knowledge of the database market will be essential during this accelerated stage of our growth.”

“OrientDB, with its combination of graph and document models, represents the next stage in the evolution of the NoSQL database.” said Jim. “I was really impressed with the mission criticality of the applications that organizations are building with OrientDB, whether it’s a tier 1 e-Commerce company that built a Recommendation Engine that combines Product Catalog data to drive increased online revenue, or a leading global bank putting OrientDB at the heart of their technology refresh applications.”

With downloads exceeding 70,000 per month, more than 100 community contributors and 1000’s of production users, Orient Technologies is experiencing tremendous growth in both community and Enterprise adoption. The native multi-model database combines the connectedness of graphs, the agility of documents and the familiar SQL dialect. Fortune 500 companies, government entities and startups all use the technology to build large-scale innovative applications. Some of their clients include Ericsson, the United Nations, Pitney Bowes, Sky, CenturyLink and Sonatype. OrientDB recently won the prestigious 2015 Infoworld Bossie Award.

Orient Technologies is the main sponsor and the commercial supporter of OrientDB.

Resources:

The post OrientDB Hires MongoDB and MarkLogic Executive as VP of Sales appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/orientdb-hires-mongodb-and-marklogic-executive-as-vp-of-sales/feed/ 0
Released OrientDB 2.1.5 http://orientdb.com/released-orientdb-2-1-5/ http://orientdb.com/released-orientdb-2-1-5/#comments Sun, 01 Nov 2015 21:13:24 +0000 http://orientdb.com/?p=13037 London, October 29, 2015 The OrientDB Team has just released OrientDB v2.1.5, resolving 27 issues from v2.1.4. This is the last stable release, please upgrade your […]

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

]]>
London, October 29, 2015

The OrientDB Team has just released OrientDB v2.1.5, resolving 27 issues from v2.1.4. This is the last stable release, please upgrade your production environments to v2.1.5. Starting from this release, ETL, Lucene and JDBC repositories are part of the core.

Below you can find the link to all the resolved issues:
Kernel (27)

Download it 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,

Luca Garulli
CEO at Orient Technologies LTD
the Company behind OrientDB

 

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

]]>
http://orientdb.com/released-orientdb-2-1-5/feed/ 0
Gartner Recognizes Orient Technologies in 2015 Magic Quadrant for Operational Database Management Systems http://orientdb.com/gartner-magic-quadrant-2015-orientdb/ http://orientdb.com/gartner-magic-quadrant-2015-orientdb/#comments Fri, 16 Oct 2015 14:00:04 +0000 http://orientdb.com/?p=12983 Placement based on completeness of vision and ability to execute London, UK (Oct 16, 2015) — Orient Technologies, the company behind OrientDB (www.orientdb.com), today […]

The post Gartner Recognizes Orient Technologies in 2015 Magic Quadrant for Operational Database Management Systems appeared first on OrientDB Multi-Model NoSQL Database.

]]>
Placement based on completeness of vision and ability to execute

London, UK (Oct 16, 2015) — Orient Technologies, the company behind OrientDB (www.orientdb.com), today announced that it has been included by Gartner in their 2015 Magic Quadrant for Operational Databases*.

Gartner defines the operational DBMS market by relational and non-relational database management products that are suitable for a broad range of enterprise-level, transactional applications. The report also highlights as a strategic planning assumption that by 2017, all leading operational DBMSs will offer multiple data models, relational and NoSQL, in a single DBMS platform.  This is a vision pioneered by OrientDB since 2010.

“The Magic Quadrant serves as a trusted resource for companies as they look for operational databases and 31 vendors have been evaluated. OrientDB pioneered the multi-model approach in 2010 and we believe being recognized by the world’s leading industry analyst validates our vision,” said Luca Olivari, President of Orient Technologies.

Orient Technologies is the only NoSQL company that has been funded exclusively by its own customers**. Research and Development activities are sponsored by clients and supported by an active user community. With relentless focus on building the operational database for tomorrow’s enterprises, OrientDB continues to grow and deliver on the multimodel vision that’s changing the database landscape forever.

About the Magic Quadrant

Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

About OrientDB

With downloads exceeding 70,000 per month, more than 100 community contributors and 1000’s of production users, Orient Technologies is experiencing tremendous growth in both Community and Enterprise adoption. The native multi-model database combines the connectedness of graphs, the agility of documents and the familiar SQL dialect. Fortune 500 companies, government entities and startups all use the technology to build large-scale innovative applications. Some of their clients include Ericsson, the United Nations, Pitney Bowes, Sky, CenturyLink and Sonatype. OrientDB recently won the prestigious 2015 Infoworld Bossie Award.

Orient Technologies is the main sponsor and the commercial supporter of OrientDB.

Resources:

• Getting Started with OrientDB Udemy Training
• Comparison with Neo4j and MongoDB
• OrientDB and OrientDB Enterprise Download
• Follow OrientDB on Twitter

*Gartner, Inc., Magic Quadrant for Operational Database Management Systems by Donald Feinberg, Merv Adrian, Nick Heudecker, Adam M. Ronthal and Terilyn Palanca, October 12, 2015.
** Company funding data taken from Crunchbase as of October 12, 2015

The post Gartner Recognizes Orient Technologies in 2015 Magic Quadrant for Operational Database Management Systems appeared first on OrientDB Multi-Model NoSQL Database.

]]>
http://orientdb.com/gartner-magic-quadrant-2015-orientdb/feed/ 0