Oracle NoSQL Database vs. RavenDB

Oracle NoSQL Database is well-suited for you if your data formats are not consistent, if you have limited hardware resources, if you higher data throughput (whether the database is on the cloud or running locally), and if you don't need a declarative query language to maintain a standardized schema of your data. If you need reduced data redundancy and require ACID compliance, you are better off finding an SQL database solution.

RavenDB is very well suited for NoSQL beginners to start easily setting up and using a NoSQL database. Also to set up a high performance and high availability cluster is possible without reading tons of documentation. Very straightforward assistant! The performance is really high.

• Data-model flexibility. Unlike RDBMS solutions, Oracle NoSQL does not restrict you to a predefined set of data types.
• Ability to Handle an Increased Amount of Traffic. As Oracle NoSQL can process queries much quicker than Oracle Database, Oracle NoSQL is able to respond to a lot more queries in the same amount of time.
• Data-model simplicity. In SQL-oriented databases, there is a learning curve in learning the relationship between databases, tables, rows, and keys. On the other hand, Oracle NoSQL's key-value based storage is much easier to get the hang of.

• Document Database - no Object-Relational Impedance Mismatch
• ACID support that is optimized for performance
• Can be easily integrated into automated tests (unit tests)
• Easily configurable via C# code
• Comes directly with RavenStudio - no SSMS or SQL Developer required
• In general low footprint when it comes to memory and disk consumption
• Useful safety nets for new developers - e.g. by default an exception is thrown when you make too many requests within a session

• Fewer analytical functions to choose from. When compared to Oracle Database, there is significant difference in the amount of built-in analytical functions.
• Eventual data consistency. It is not guaranteed that a write or delete query will be immediately visible for subsequent queries.
• Data redundancy. As there are no mechanisms that insure data integrity, users are more likely to have redundant data across their documents.

• Developing methods is challenging if developers are unfamiliar with the accurate simulation approach.
• It does not allow you to replicating, or authorized access without first acquiring a license.
• The lack of evidence of tracking records in the enterprise systems raises several concerns about RavenDB.

We've had an excellent experience using RavenDB. Internally we are testing the newer features in 5.0 such as time series, which will effect the con specified previously dependent on the real world performance. We foresee that BattleCrate will continue to use RavenDB as we grow.

Really good .NET client that is very easy to use. The management studio is excellent and puts anything that Microsoft or Oracle have to shame. Very quick to develop with once the complexity hurdle has been overcome. Initially using it can be a bit painful until you fully grasp the event sourced nature of the indexing.

Had a question that was answered in minutes. Never used a NoSQL approach before, but was able to be proficient in a matter of hours. Easy to read API Documentation. 5 out 5 support in book, I have never once ran into an issue that wasn't quickly solved by either their support team or myself doing a quick search online.

RavenFS changed along the way and made us change the codes.

I have not used any other types of NoSQL databases.

RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. RavenDB is a storage system designed for the current websites and functional prototypes. It has an easy-to-use interface and enables quick replication and backup installation. Furthermore, technical assistance responds quickly and walks you through the implementation and deployment procedures.

• We pay less for computing resources, as Oracle NoSQL databases respond quicker than our previous SQL databases.
• Our database administrators and software developers do not need to worry about "data massaging" and can focus on perfecting application logic.
• Oracle NoSQL has built-in integration to other Oracle products, so we didn't not need to spend money on building custom integrators or higher additional developers.

• RavenDB has saved my customers a lot of money with their cloud services' tiered model. The database is able to grow with the project/company and can start out small at a low cost.
• RavenDB is free for three nodes and three CPUs, which makes it great for development scenarios. You're able to start rapidly building applications without having to worry about licensing.
• Scaling out has allowed us to use three small cloud servers when starting out and get the performance and throughput of a single larger server.