Understanding the strengths, limitations and trade-offs among the leading DBMS options can be DIS-ORIENTING. Developers have grown tired of making compromises in speed and flexibility or supporting several DBMS products to satisfy their use case requirements.
Thus, OrientDB was born: the first Multi-Model Open Source NoSQL DBMS that combines the power of graphs and the flexibility of documents into one scalable, high-performance operational database.
OrientDB was engineered from the ground up with performance as a key specification. It’s fast on both read and write operations. On writes, it can store up to 150,000 records per second*. The OrientDB time series module can insert 120,000 records per second*, while keeping the time graph synchronized for real-time analytics.
No More Joins
OrientDB can embed documents like any other document database, but also supports relationships. It doesn’t use the costly JOIN. Instead, OrientDB uses super-fast, persistent pointers between records, taken from the graph database world. You can traverse parts of or entire trees and graphs of records in just a few milliseconds.
This illustration shows how the original document has been split into two documents linked using the Customer’s Record ID #8:124 to connect the Order to the Customer document. Links can be thought of as in-memory pointers, but persistent on disk.
Why connect documents rather than embedding them? To avoid duplicates. The resulting database is smaller, lighter and faster, with better use of RAM resulting in more effective caching. Upon loading a tree of documents, OrientDB will assemble the entire document structure by fetching all connections transparently.
Big Data Equipped
With document and relational DBMS, the more data you have, the slower the database will be. Joins have a heavy runtime cost. Instead, OrientDB handles relationships as physical links to the records, assigned only once, when the edge is created O(1). Compare this to an RDBMS that “computes“ the relationship every single time you query a database O(LogN). With OrientDB, traversing speed is not affected by the database size. It is always constant, whether for one record or 100 billion records. This is critical in the age of Big Data!
Download the XGDBench: A Benchmarking Platform for Graph Stores in Exascale Clouds by Tokyo Institute of Technology and IBM Research.
Replacing your DBMS, once it no longer meets requirements, can be a huge cost in time and resources. Is your database powerful, scalable and flexible enough to grow with you? Using OrientDB also reduces the need to support multiple products to achieve your goals.
|Features & Capabilities||OrientDB||MongoDB||Neo4j||MySQL (RDBMS)|
|Schema-full, Schema-less, Schema mix|
|User and Role Security|
|Record Level Security|
|Record Level Locking|
|TinkerPop Gremlin language|
|Relationships (Linked Documents)|
|Custom Data Types|
|Elastic Scalability with Zero Configuration|
|Native HTTP Rest/JSON|
|Commercial Friendly License|
|Embeddable with No Restrictions|
OrientDB supports a Multi-Master + Sharded architecture, so all the servers are masters. This provides horizontal scalability and reliability.
Elastic Linear Scalability
With a master-slave architecture, the master often becomes the bottleneck. With OrientDB, throughput is not limited by a single server. Global throughput is the sum of the throughput of all the servers. If you want to scale up, simply add a server node in the network and it will automatically join the existing distributed server cluster with zero configuration. Synchronization occurs automatically as soon as the server is brought online.
The transactional engine can run in distributed systems supporting up to
302,231,454,903,657 billion (2^78) records for maximum capacity of 19,807,040,628,566 Petabytes of data distributed on multiple disks in multiple nodes.
Most NoSQL solutions are used as “cache” to speed up certain use cases, while the master database remains a relational DBMS. For this reason, the average NoSQL product is built more for performance and scalability, while sacrificing reliability.
OrientDB, however, isn’t the average NoSQL DBMS. What happens when a server node crashes? Thanks to WAL (Write Ahead Logging), OrientDB is able to restore the database content after a crash. Any pending transactions are automatically rolled back. Immediately, the server cluster redistributes the load across the available nodes and all the clients connected to the node in failure are automatically switched to an available server node with no fail-over to the application level.
Perfect Cloud Database Solution
Due to the previously mentioned benefits provided by the zero-config multi-master architecture, OrientDB is perfect for the Cloud. Hundreds of servers can share the workload, scaling horizontally across distributed modern data centers. View our Cloud partners.
OrientDB is written entirely in Java and can run on any platform without configuration and installation. It’s a drop in replacement for the most common existing graph databases in deployment today. The Full Server distribution is about 2MB without the demo database. Do you develop with a language other than Java? No problem. Take a look at the Programming Language Bindings for additional options.
OrientDB focuses on standards when it comes to query languages. SQL is widely used and well understood, so we extended it to also include graph functionality. Alternately, you can also use the Tinkerpop API which is a standard among most graph databases. Staying in line with standards is always a good choice.
You can start working with OrientDB in just a few hours. Just take an Online Course or get started with our OrientDB Manual. Join OrientDB’s User Community, comprised of more than 2,000 users worldwide, to ask for help, post your ideas, or share your experience.
There is absolutely no cost associated with using OrientDB Community Edition. OrientDB is distributed with only one license: Apache 2 Open Source. This is one of the most liberal licenses available, allowing you to use OrientDB FREE for any purpose.
Due to its feature-rich, multi-model design, using OrientDB reduces the need to support multiple products to achieve your goals. The ease of use, zero-configuration multi-master architecture, and SQL based query language make OrientDB an ideal default choice. Orient Technologies, the company behind OrientDB, offers optional services such as Developer and Production Support and Training with transparent pricing far below our competitors to ensure you’re maximizing OrientDB’s capabilities for your particular use case.
While most NoSQL DBMSs are used as secondary databases, OrientDB is powerful and flexible enough to be used as an operational DBMS. It doesn’t require a restart or down-time for maintenance and it automatically reuses free space left by deleted records while still online.
OrientDB Enterprise edition is commercial software built on top of the Community edition, developed by the same team that created the OrientDB engine. It serves as an extension of the Community Edition by providing Enterprise features such as: Query Profiler, Distributed Clustering configuration, Metrics Recording, and Live Monitoring with configurable Alerts. Enterprise Edition is free with Support.
Nothing available on the market comes close to OrientDB in regards to feature offerings, nor has our transparent competitive pricing. It would take combining several different competitive DBMS products to give you the same functionality. How does OrientDB compare to MongoDB? Take a look at OrientDB vs MongoDB. If you are already familiar with Neo4j, check out the OrientDB vs Neo4j comparison.
OrientDB is the first ever multi-model product on the market and is now leading the 2nd generation NoSQL product movement. Most NoSQL products are used to provide scalability to applications sitting on a relational DBMS. Complex 2nd generation NoSQL products like OrientDB are the future: providing more functionality and flexibility, while being powerful enough to replace your operational DBMS.
The team behind OrientDB started working with storage algorithms in 1998. The first production-ready version of OrientDB was released in early 2010. Since the first publication date, Orient Technologies has published more than 60 releases (an average of 2-3 major releases and 15 minor releases each year). What you see today, is a product based on 16 years of research and constant adaptation to user demand and the latest technology available. If you look at our history, OrientDB has proven its staying power and its innovations have raised the bar tremendously, forcing other NoSQL products to offer more functionality in order to remain competitive in the market.
Which is more likely to have better quality? A DBMS created and tested by a handful of developers or by 1000’s of developers? When code is public and transparent, everyone can scrutinize, test, report and resolve issues. Things move faster compared to the proprietary world.***
OrientDB’s Active User Community, comprised of 70 contributors and thousands of active users worldwide, is extraordinary. Our developers are a completely different class of techie. After performing an exhaustive due diligence, they selected OrientDB for its technical superiority. Now they contribute to improve the product’s stability and help innovate by adding new features, drivers, etc. Their enhancement requests became our unmatched feature offerings, making OrientDB what it is today: a 2nd generation multi-model Open Source NoSQL product.
Orient Technologies leads the open source project and defines the roadmap. All members of the Orient Technologies Development Team were original contributors to the OrientDB Open Source project years before being brought onto the team. Their expert product knowledge coupled with the passion they bring to the table everyday, ensure quality in the product, support and consultancy work.
“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
OrientDB is privately funded and the first graph database ever to be listed on Gartner’s Operational DBMS Magic Quadrant in 2013.** How is it possible to successfully compete against DBMS products that have multimillions in venture capital funds, all while maintaining ZERO debt?
When the only obligation is to the clients, it’s easy to keep your priorities in the right place. Effort is focused on building a high-quality, innovative product, while our clients and users do our marketing for us. Since all Orient Technologies sales are based on word-of-mouth or incoming inquiries, OrientDB’s international reputation for having unmatched technical capabilities has been paramount in its success. We’re 100% dependent on client satisfaction, so prompt support assistance and quick issue resolution is absolutely critical to our business.
“…and possibly the biggest innovation since the 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.” – Why OrientDB is important
* On Common hardware (laptop with 4 core CPU, 8 GB RAM, HDD7200 RPM)
** Gartner, Magic Quadrant for Operational Database Management System, Donald Feinberg, et al, October 21, 2013.
*** Source: http://www.pcworld.com/article/209891/10_reasons_open_source_is_good_for_business.html