Likelihood to Recommend For running application tests it's well suited. H2 [Database Engine] can replace the real-world database solution for them easily and removes the requirement to set up a a separate database instance just for running unit tests. For using in actual production application one needs to consider scale. H2 is suitable if application runs in single instance and database is located in same machine as a file where that application runs. This means the application shouldn't have a large user base. However it's easy to switch to an actual
MySQL instance if the need arises, it's most likely only a configuration change and doesn't require new code.
Read full review If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.
Read full review Pros Can run as an in-memory database. Simple and quick to get started with, and is light weight (only 2MB). SQL compliant so it compatible with most relational databases. Read full review Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet. Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management. Read full review Cons There's a warning in official FAQ "Is it Reliable?"-section which makes it seem like H2 is not yet a mature product. If raw SQL queries are used there maybe be differences between MySQL & H2. ORM library should be used. Support seems to be community-based only. Read full review An aggregate pipeline can be a bit overwhelming as a newcomer. There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close. Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty. Read full review Likelihood to Renew I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.
Read full review Usability NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.
Read full review Support Rating Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.
Read full review Implementation Rating While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
Tom Maiaroto Sr. Platform Developer / UX Designer / Optimization Engineer
Read full review Alternatives Considered While both can run as an in-memory database, H2 Database Engine was just so much easier for us to use since we primarily use the Java stack and H2 Database Engine is also built with Java.
Read full review We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need
Cassandra .
Cassandra 's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation;
Cassandra provides native Hadoop support.
Read full review Return on Investment Doesn't take time from developers, once it's configs are set up for testing it works in everyone's development environments Easy to integrate in application, no need to setup separate database software, no maintenance No need to deal with infrastructure related issues/costs - database runs in same machine as the application that uses it. Read full review Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models) You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB Read full review ScreenShots