Case Studies & Whitepapers

axon_250_250

Massiv.io

Quickly and efficiently process & query complex, interrelated code while clustering data in a cloud environment is no easy task. While other pure graph databases might prove adequate for some applications, modern day, embeddable applications demand that clusters of highly interconnected data to be traversed incrementally.

Testing graph databases to find the right solution is no easy process. Discover how OrientDB can provide critical features and help save precious development time.

Diaku Axon

Your data is only as good as what you can do with it. Enterprises must make use of multiple systems to carry out daily operations and rely heavily on relational databases to store their master data. However, rapidly growing and ever-changing data makes these systems difficult to adapt and usually result in lost business insights, missed opportunities, as well as inefficient workplace practices.

Whether it’s company hierarchies, teams, projects, sales, or accounts, reallife relations are naturally evident in a graph. See how OrientDB handles the challenges of today’s big data world.

Fraud Prevention

Fraudster are constantly developing new methods to exploit week data links, create false identities and develop elaborate schemes. RDBMS systems are simply not capable of quickly exploring relations to uncover crimes such as fraud rings or identity theft. For that, you need a graph database in order to navigate connections in real time to discover patterns, match data and stop fraud before it happens.

With new enhanced security features introduced in OrientDB 2.2, your (and your clients) data is safe from fraudulent actions.

Traffic Mgmt.

How do traffic management systems handle the tremendous amount of data needed to improve the flow of traffic and reduce congestion in areas such as freeways, busy city streets and urban areas? OrientDB’s multi-model approach combines graph and document models, creating a unique method that enables systems to discover new time related dimensions as well as tackle complex forecasting.

Find out how OrientDB can effectively analyze real-time traffic data.

 

Success Stories

See what others say about OrientDB and how they are using it. Also, take a look at the Clients who are using OrientDB in production.

National Institutes of Heath US Department of Health and Human Services

"New technologies such as the MVRB-tree algorithm implemented in the OrientDB graph database have proved far more efficient and scalable than the traditional relational data base management system..."

- Scott Bauer, National Institutes of Heath US Department of Health and Human Services

The Mysteries of Big Data and the OrientDB

"...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

Why I use OrientDB in Production

"I narrowed my choices to OrientDB and Neo4j. It’s been a couple years since that decision process occurred, but I distinctly remember a few reasons why I ultimately chose OrientDB over Neo4j: Performance benchmarks for OrientDB were very impressive, The OrientDB development team was very active, Cost: OrientDB is free. Neo4j cost more than what I was willing to pay or what I could afford. I forget which it was..."

Dave Sims - Founder and CEO, Floify

UltraDNS
Using OrientDB in UltraDNS: "as a result our DNS server was able to move to a model that keeps almost every zone in memory while serving the data out of a lock-free pipeline. This yielded significant performance improvement that resulted in a >7x QPS processing capacity on a per DNS server basis."

- Jeffrey Damick, Neustar Principal Software Engineer (Source)

Axon (Diaku) uses OrientDB
"...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

OpenChrom
"I really appreciate to use OrientDB, due to the point, that it can be integrated very easily and that it is written in Java. Moreover, user defined databases can be created on-the-fly. Great. A big benefit is, that the configuration can be hidden from the user. Which user wants to setup a MySQL or MongoDB previously? Furthermore, my users most commonly don't have the capabilities to do that."

- Dr. Philip Wenig, Founder of @OpenChrom

BaasBox
"We have chosen OrientDB because we needed a Graph database to manage relationships among documents in a simple ed efficient way. Furthermore we needed an embeddable engine with a non-limiting license due to our business model. OrientDB matches all our criteria and over. Its team is always available, very active and always ready to give support about doubts and questions."

- Claudio Tesoriero, founder @BaasBox

GrandSLA
"OrientDB appealed to us because of its flexibility and performances. Creating mixed schema data structures suits our needs. Traverse operations and fetch strategies are extremely efficient and easy to use. Last but not least, we speed up the coding phase comparing with a traditional RDBMS approach. In short, a Five Star Product."

- Fabrizio Fortino, Chief Developer @GRANDSLA

Awal Technologies
"I am glad we didn’t have a learn some aliens language like Cypher to traverse and find patterns out of the relationships. It has a simple SQL like language to do the stuff we needed. This same was very difficult and painful to do using BigTable like DBMSs e.g. HyperTable and HBase. Obviously we are not talking about hundreds of petabytes of data here. While MongoDB was notorious about data lose, because of its late data flushing out to disk. So we tried CouchDB, but we very disappointed to see how we had to query data using its improperly implemented Map-Reduce querying feature. Neo4J is a good product to drain out your money and still keep you unsatisfied, due to its non-distributed nature. So we were left with OrientDB as the single and the best choice for our problems solution." - Kashif Masood Technical Executive at Awal Technologies
OpenEMPI
"Before we selected OrientDB we developed a few prototypes to evaluate the performance of the database in being able to efficiently handle large volumes of records of data where the precise field composition of each record is specified by the user during deployment. We evaluated both relational databases and a couple of NoSQL database and OrientDB was clearly the best option. The flexible Apache license was also another key reason why we made the selection. Finally, the fact that OrientDB is supported by such a dedicated group of people who also provide commercial support if needed, was the feature that closed the deal." - Odysseas Pentakalos, CTO at SYSNET International