"Enhanced security is the key new feature of the new release. OrientDB Enterprise Auditing feature allows customers to track Create, Read, Update and Delete (CRUD) operations on every object. Polymorphic auditing allows objects to inherit auditing directives, further simplifying policy definitions. Version 2.1 also includes 24×7 global support services (previous support model was 8x5)."
- Srini Penchikala
"OrientDB is an interesting hybrid in the NoSQL world, combining features from a document database, where individual documents can have multiple fields without necessarily defining a schema, and a graph database, which consists of a set of nodes and edges. At a basic level, OrientDB considers the document as a vertex, and relationships between fields as graph edges. Because the relationships between elements are part of the record, no costly joins are required when querying data..."
"...There will always be databases that solve a niche problem extremely well, but we need a solution to become the operational datastore of the modern enterprise. Multi-model databases, in general, and OrientDB, in particular, have what it takes to become a viable alternative to RDBMS and succeed first generation NoSQL products..."
- Matt Asay
"...OrientDB does something similar, but packages itself as a "second-generation graph database." In other words, the nodes in the graphs are documents waiting for arbitrary key-value pairs. This makes OrientDB feel like a graph database first, but there's no reason you can't use the key-value store alone. They also include a RESTful API waiting for your queries..."
- Peter Wayner
"OrientDB’s CEO and Founder Luca Garulli took a moment to tell us about OrientDB – what it is and what it does – and why it’s not technically just a NoSQL DBMS but rather a multi-model database management."
"In this new story, I want to show you how much it is simple today to build and deploy your own modern and scalable platform. In the following lines I will present an industrial-strength and future-proof technology stack that is based on both Wisdom Framework, OrientDB and Docker technologies..."
"Overall I’m impressed with OrientDB and its performance metrics look pretty amazing, either on par with or better than Neo4j. I am using the SQL syntax but I’ve only had a few hours of exposure so I’m betting the above query could be refactored into something more elegant by people who know more idiomatic ways of doing things. I’m definitely going to continue looking into OrientDB"
- Kevin Hoffman
"...Neo4j has cornered the market... In truth there aren't many alternatives out there, but alternatives exist. OrientDB is a hybrid graph document database that offers the unique flexibility of modeling data in the form of either documents, or graphs, while incorporating object-oriented programming as a way of encapsulating relationships. Again, it's a great example of developers imagining ways in which we can accommodate the myriad of different data types, and relationships that connect it all together."
- Julian Ursell - Category Editor at Packt Publishing
"...Which brings me back to OrientDB: when you have multiple processes and multiple people undertaking multiple tasks against multiple data sources, then doing things like impact analysis (which Axon supports) can get quite complex. Without a graph capability of some kind it can easily become too difficult and slow to explore the environment."
Philip Howard - Research Director at Bloor Research
"...Although MongoDB, CouchDB, Neo4J are some of the popular NoSQL DBs, but if we get into details and compare them I personally think OrientDB is much better. Against MongoDB which makes a good case only for WORM (Write Once, Read Many) applications, OrientDB stand out. When we store related data in MongoDB, either we embed the sub document in parent document (we make data de-normalized, not good for updates or multiple writes) or we build relation between documents using reference (which are resolved at run time and hits the read performance). On other hand OrientDB handles it differently. As every record / document in OrientDB is an object (instance of a class) the linking between objects / documents is not through references, its direct linking (saving pointer to object. This this leads to quick retrieval of related data as compared to JOINS in RDBMS. So OrientDB neither loose the benefits of normalization and nor it gets hit on read / query performance due to run time cost of JOINS (there are no joins, it stored the direct pointers to other related documents)..."
...Through the combined use of Apache Hadoop, the ElasticSearch search engine,and the OrientDB graph-oriented database, we can acquire, link, and index all of a company’s customer information. We use all available data sources – internal (claims, CRM, and portfolio systems) and external (a blacklist to give the company the option both to execute antifraud rules to identify suspicious links and to graphically visualize those connections. In the prototype, more than 60 million documents were indexed and about 15 million relationships appeared in the final network....
...You should now have a good idea of how to work with a OrientDB database system. As you can see, it blends many elements from different systems. It keeps SQL select querying syntax, while leveraging traditional NoSQL document storage, and builds graph relational behavior. This has only been a brief introduction meant to introduce you to some of the ways that OrientDB can operate on data. The project's documentation is a great resource for building off of this introduction.
When developing software it is important to choose the right technologies. With recent projects we have been working with various databases namely MongoDB, RavenDB, Couchbase, Redis and of course the standard MySQL, Postgresql and SQL Server. As if these were not enough, we also are looking at ArangoDB, Neo4j and possibly the biggest innovation since microchip (or sliced bread) called OrientDB.... OrientDB stands to be the most important database on market right now, nothing short of the future of databases...
There has been something of a database renaissance in recent years, as big data requirements have emerged so have non-relational databases and terms such as "NoSQL", "document" and "graph" scatter the landscape. Earlier this year we decided to invest some time into researching an exciting and innovative database that combines all three terms into an open source product that is currently used in production by large companies and startups alike - OrientDB...
Every now and then you come across open source projects that just amazes you. OrientDB is one of these projects.
I’ve always assumed that I’d have to use a polyglot persistence model in complex applications. I’d use a graph database if I want to traverse the information, I’d use a document database when I want schema less complex structures, and the list goes on...
In this post, I am going to give you a brief introduction to a OrientDB. In later posts in this series, I will take you through using OrientDB with Ruby. You have probably heard of document databases, like MongoDB, and you may have heard of graph databases, like Neo4j. I am willing to bet you have not heard of very many, if any, Graph-Document databases.
That’s right. OrientDB touts itself as “The Graph-Document NoSQL.” ...
During some unfocussed searches I happened across OrientDB which claims to be a document-based database but with support for relationships, which addressed the requirements more fully. Further investigation revealed an entire ecosystem existed for OrientDB, including OrientDB drivers for pretty much every mainstream language and framework...
We’re heading East for our next examination of a noSQL DBMS. Oddly enough, OrientDB’s roots are not in the orient. The boot-shaped country of Italy is where this noSQL database was born. Before diving in to what makes OrientDB unique, you may want to check out our last trip (featuring MongoDB) and some supporting material that discusses noSQL’s relevance...