Home/ Graph Database/ OrientDB/ Reviews
A simple DBMS to learn NoSQL Database
44.3%
36.1%
11.5%
8.2%
0%
Fast Query Performance, SQL-Like Query Language, Multi-Model Capabilities, Easy Integration
Poor Documentation, Stability Issues, Limited Driver Support, Small Community
OrientDB user reviews highlight its strengths in handling complex relationships and hierarchical data structures, particularly for applications requiring fast data retrieval. Users praise its ease of use, particularly for developers familiar with SQL and Java, and its ability to integrate with various programming languages. However, concerns exist regarding documentation, stability, and scalability, with some users experiencing performance issues at large data sizes. OrientDB's multi-model approach offers versatility, but its hybrid nature can lead to complexities. While some users find the GUI helpful, others lament its limited capabilities and the lack of an installable application.
AI-Generated from the text of User Reviews
We use orient db as cache memory which insert and fetch data at lightning speed. Also graphical data solved lot of problems
Nothing as such, all are prons I don’t see any cons
We use orient db as cache memory which insert and fetch data at lightning speed. Also graphical data solved lot of problems
The multi model graph-based design is my favourite aspect. It allows me to easily follow the document database. The identification, passwords and encryption ensures our date remains confidential.
Can be a very costly program to run however it's worth it!
Using the teleporter tool we've been able to modernise our database by migrating them a lot more efficiently than we had imagined.
OrientDB has a really friendly licence. This is essential for our research purposes. The main aspects we have liked is that OrientDB is easy to understand and to use. It combines schemas, documents and graphs in an easy and simple way. In addition, it is well documented and has a large community providing support.
More than dislike, I think it is a feature request :). OrientDB has already integration with Python and is compliant with Apache TinkerPop. We hope new versions of OrientDB will bring higher integration with specific Python tools such as NetworkX.
We have been working in the H2020 project MixedEmotions (http://mixedemotions.insight-centre.org/modules) for analyzing the social context of users, that is, how emotions are propagated in the network. OrientDB has been used for storing and retrieving ego networks. Analyzing how emotions are propagated is used for marketing, brand monitoring, radicalism detection, etc.
Quite easy to install.
It has good drivers for working with various programming languages, and also a great plus is the ability to work through REST.
A mixed model is an excellent solution for storing complex data, and built-in classes and inheritance solve many problems.
It is very convenient to work using SQL like requests.
Weak documentation. Many powerful things are simply not described in it.
Use it, if you need the best graph database engine
Work with large amounts of data. Quick search of results in the graph. Convenient use with several programming languages.
We’re a consultancy company who helps clients adopt Big Data technologies, and Graph is increasingly becoming an important aspect of the data-stack; especially for complex and connected data-sets such social network applications and analysis. We have a number of customers using Orient with 50-million + node/relationship workloads. We’ve worked with all the major Graph platforms and Orient is currently our preferred choice. Performance is great and the query language, being a hybrid of standard SQL & Graph means adoption is easier than if using Gremlin or Cypher, both of which look great at first but query complexity can escalate rapidly. Orient’s mix works in practice. Another feature we like is the ability to query it via standard JDBC connections, which means standard tools such as DB Visualizer work; which just make using it more pleasurable than rivals. We develop in Java, and their APIs are rock solid. Pricing is also more reasonable that rivals; making horizontal distribution more practical.
Sometimes the Orient Studio forgets the visualisation settings for the Graph so all the lovely setup work you’ve done to make it look pretty gets lost. Sort it out Orient!
We use Orient for its Graph capabilities, where Orient is very fast. Make sure you understand Graph query and why you'd use them.
Various types of network analysis, both for commercial and government. We’re also looking at helping to implement social network style features and newsfeeds, the recursive nature of which Graph is perfectly suited for.
This is an easy to install DB.
The fact that it's SQL is very close to relational SQL makes it easy to use to most developers.
The results from querys are extremely fast.
Graph and Document characteristics combined make this DB very unique.
Embeded maps are extremely useful.
Drivers are a down side in this datababse. Connector drivers should be improved - but this should not stop you from choosing this DB.
OrientDB's documentation is not always up to date.
There is no import button in Orient Studio. Imports must be run manually.
Changing attribute names can cause problems.
If you are looking for a flexible database, quick to learn, easy to migrate from other databases, this is the one.
Another thumbs up is the fact that it is free.
Big Data, database analysis, graph database / non-relational data structure, fast development.
1. Elaborated documents for a beginner without any graph background knowledge to grasp basic graph theory and orientdb practice.
2. Build on Java platform, which is our company's main dev language as well, it's too easy to spend much time customizing various implementation as we demand.
The infrastructural graph engine/model can't support too much online real-time concurrency(OLTP), especially when facing to plenty of edges concurrency maintenance on super node.
As of now, we can realize real-time in other way, it'll be just perfect if someday orientdb support high-concurrency well.
Although orientdb is still not the top1 graphdb in market, its rising trend cannot be ignored. It has proved that the customers and market admits its abilities and features, whatever multi-model, or ease of use, or powerful graph traverse engine, or distributed architecture. Almost every element with regards to internet technologies is introduced in. What are you waiting for?
Since we're a financial company, the scenarios we leverage orientdb to satisfy are:
1. anti-fraud, based on transactions, payment, orders, GPS, phone call, etc. Actually this is similar and applied to any social network model.
2. RPC invoke chain, collecting rpc invoke records into orientdb, analyzing the bottlenecks or design issues.
1. Elaborated documents for a beginner without any graph background knowledge to grasp basic graph theory and orientdb practice.
2. Build on Java platform, which is our company's main dev language as well, it's too easy to spend much time customizing various implementation as we demand.
The infrastructural graph engine/model can't support too much online real-time concurrency(OLTP), especially when facing to plenty of edges concurrency maintenance on super node.
As of now, we can realize real-time in other way, it'll be just perfect if someday orientdb support high-concurrency well.
Although orientdb is still not the top1 graphdb in market, its rising trend cannot be ignored. It has proved that the customers and market admits its abilities and features, whatever multi-model, or ease of use, or powerful graph traverse engine, or distributed architecture. Almost every element with regards to internet technologies is introduced in. What are you waiting for?
Since we're a financial company, the scenarios we leverage orientdb to satisfy are:
1. anti-fraud, based on transactions, payment, orders, GPS, phone call, etc. Actually this is similar and applied to any social network model.
2. RPC invoke chain, collecting rpc invoke records into orientdb, analyzing the bottlenecks or design issues.
Multi model Nosql database as we can trust in our operational business . The best performance in graph , document , indexing , read and write with intensive data .
Documentation integration and lack of examples , best practices and social tutorial system .
if you want to choose a right product for Operational Database and working with graph , documents , key-value , spatial , analytical with the painless configuration and a good support in communities , i suggest to use OrientDB in your business environment .
If you be familiar with the simple and basic concept of OrientDB in operation , you can easily switch to achieve more performance in read and write iops as you reached .
We have use OrientDB in a CMS and a Mobile location based service .
our CMS service use OrientDB document base features actually . the highest read and write is our founded benefit in OrientDB .
In the location and mobile based scenario we used orientdb graph and spatial features too .
There are several function for working the graphs like the shortest path , Dijkstra , A* and many standard Geo spatial functions in OrientDB that provides facilty and ease of use to making a business better .
OrientDB is a open source and live database project in github so we can contribute to growing together . we can write modules , functions or report our issues to orientdb project and receive a nice , fast and friendly online support .
OrientDB have a native and official support for wide range of developing platforms . as we experienced with nodejs and java api , we can develop our software and services and connect fast and secure to orientdb remotely and easily.
Looking for the right SaaS
We can help you choose the best SaaS for your specific requirements. Our in-house experts will assist you with their hand-picked recommendations.
Want more customers?
Our experts will research about your product and list it on SaaSworthy for FREE.
I liked that OrientDB did everything - Graph Db, Key based, Document based. Plus it had elastic search built in. Additionally, the studio has a graphical user interface to the graph DB itself. This helped to visually understand how things were working when you saved objects and created connections.
The documentation is horrible
features of database that are not documented and I found them on forums
DB seems very powerful but the documentation is bad
Wish I didn't need a java based server to run orientdb
It can be expensive to host OrientDB
Make sure you can understand documentation. Try to understand the documentation well and understand how to query the graph based DB in multiple ways which can be very powerful.
connecting people in a social network. Speed and ease to do everything in one DB.
I was able to create a social network which need connections tracked, geolocation search, and text search. Therefore ORIENTDB fit all the criteria and I experimented with it. The document structure was used to store information on users and their posts. The graph based DB was used to store connection between users and their post's connections to other posts based on likeness. I used the apache search to search text within users' posts which was done to find likeness and then connect them up using the the Graph DB structure. I also integrated socketio to provide a realtime response in my web application.