HBase vs SQLite

• 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

• The biggest one has to be that it is freeware and open source as well. It means for an entry level person who wants to learn relational database and even for a team in the early development stage where security and size of the data are not much, it is a perfect fit in those cases.
• It requires no extra configuration or space because it a server-less installation and also done in just a few mins. So, installing this is never a blocker. It is the actual lite version of SQL as the name suggests and it very powerful and capable of doing all the things which SQL can do, but lacks some of the security and advanced features.
• It prepares the data for us in a structured form in terms of Tables with a file size less than 1 Mb for the complete database entries. It saves us a lot of physical space.
• It is the most suitable DB for Android systems because mobile apps do not have a lot of space or resources for a separate DB, but this one integrates with the whole ecosystem very nicely and we are able to make the most out of it and that too with a file lesser than 1 Mb in size.

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

• Better data recovery when the database becomes corrupt would be ideal. I've learned to minimize it by closing the database more frequently, but it can still happen.
• Lack of built-in data encryption.
• SQLite is a single-user DBMS. If a multi-user system is required, then an alternative is required.

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

• We could start immediately to work with SQLite.
• It's very easy. The document is well done and easy to find.
• Having such good database system, free of charge and for any purpose is good news.

Read full review