Likelihood to Recommend AWS Document DB (with
MongoDB compatibility) is well suited when for all the workloads due to its huge feature offerings which will reduce our operational overhead and due to that we can focus more on our WorkLoad rather than optimising and fine tuning Databases. Its Offerings are Advanced Monitoring, DB cluster Upgrades, Migration Assistant, High Availability, Fault Tolerance, Data Durability, Security, Storage Auto Scaling, Backup Restore policies.AWS Document DB (with
MongoDB compatibility) some of the features that are there in some other services like
MongoDB Atlas that offers vast amount of features plus Supports Multi Cloud while Deploying Database clusters, Immediate support to latest Mongo DB versions, Mobile & Edge Sync like
Atlas Edge Sync, Freedom to choose Database deployment in Any top Public Cloud, Having more then 100 plus Monitoring and Telemetry metrics for index and schema recommendations, More Compatibility with
MongoDB queries.
Read full review Hbase is well suited for large organizations with millions of operations performing on tables, real-time lookup of records in a table, range queries, random reads and writes and online analytics operations. Hbase cannot be replaced for traditional databases as it cannot support all the features, CPU and memory intensive. Observed increased latency when using with MapReduce job joins.
Read full review Pros Amazon DocumentDB (with MongoDB compatibility) provides Auto scaling of cluster as a by default functionality through this we can focus on more on our applications end Through AWS Document DB without much operation overhead we can configure for Database's high availability, Durability, Backup Restores policies, Advanced Monitoring, Security Parameters. Also they can provide us a Guide for Database Migration from any Supported Mongo DB vendor to AWS Document DB. Via AWS Document DB query Logging ( Profiling ) we can fine tune our database queries and hence improving our END to END Customer Experience and Product Enhancements. Read full review Scalability. HBase can scale to trillions of records. Fast. HBase is extremely fast to scan values or retrieve individual records by key. HBase can be accessed by standard SQL via Apache Phoenix. Integrated. I can easily store and retrieve data from HBase using Apache Spark. It is easy to set up DR and backups. Ingest. It is easy to ingest data into HBase via shell, Java, Apache NiFi, Storm, Spark, Flink, Python and other means. Read full review Cons Give support for Latest Mongo DB versions available in market AWS Document DB is limited up to 32 shards per cluster and 2 shards per Document DB instance and all within single region Start supporting more numbers of Rich data types Should have access to MongoDB experts who throw light on Cutting edge mongoDB features and integration consulting. Read full review There are very few commands in HBase. Stored procedures functionality is not available so it should be implemented. HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies. Read full review Likelihood to Renew There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.
Read full review Alternatives Considered Cassandra os great for writes. But with large datasets, depending, not as great as HBASE.
Cassandra does support parquet now. HBase still performance issues.
Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
Read full review Return on Investment Great Customer Experience as DB queries are fine tuned Less Operational Overhead to manage and take care of the Database Automatic applying of Small patches Read full review As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data. Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here. The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle. Read full review ScreenShots Amazon DocumentDB (with MongoDB compatibility) Screenshots