Difference Between RDBMS and HBase

In this video we are discussing the difference between RDBMS and HBAS

So let us go for one comparison table for the better understanding

So here the first column is denoting the features of HBS and the second column is denoting

the features of RDBMS. So this is column oriented. We know that HBIS is column oriented, no SQL, non-relational distributed database

So it is a column-oriented database. in case of ADBMS, it is row-oriented. In case of H-base, we can add columns easily as when

required, so it is less restrictive. But in case of ADBMS, restriction is very high while

adding columns because the schema is more restrictive and schema is static. When we need more

processing power and dig space, we can add more hardware with a cluster without upgrading

the present one. So, here we can add more processing power. commodity hardwares, so the storing cost will be lesser, the hardware cost will be lesser

in that case, and in this way we can have more processing power

But in case of ADBMS, when we need more processing power and Dix base, we need to upgrade

the same server, not adding other commodity hardwares. HBass is good for with the sparse table, that means whenever we are having multiple null values

So for those sparse tables, HBES is very much. efficient but RDBMAS is not optimized for the sparse tables

Next point is that the size of data depends on number of machines and here the size

of data depends on the dick size of the server. So here the data will get replicated will be distributed onto multiple different nodes So that why the size of the data depends upon the number of machines not on the dig space of the server It this supports the structured and unstructured

data. We know that structured data means our database. You can consider a database as an example

of structured data. And in case of unstructured data, it might be a text file, might be a PDF

might be one image, or your videos. So it supports both structural

structured and unstructured data. But on the other hand, in case of RDBMS, this supports the structured data only

So, here you can find that this is no transaction guarantee and there is no transaction guarantee in case of HBS and it guarantees the transaction integrity

So this transaction integrity is guaranteed for ADBMS, but there is no guarantee for transaction integrity in case of HBMS

So, that's why HBs is not suitable for those applications where frequent and huge number

of transactions are going to take place. So, there is no building support for referential integrity and it supports the referential integrity

We know that referential integrity means there is a foreign key, that means prime attribute

in one table, if it is a non-prime attribute in another table, then in the second table where

it is non-prime, there it will be called as a foreign key. So that conception was there in case of RDB

So, in the respective foreign key column, we cannot put any value which is not belonging

to the primary key column of the other table. So, that is known as the differential integrity

So, DBMS supports a referential integrity, but that is no built in support for

a referential integrity in case of edge base. So in this way, we have discussed that what are the differences between the RDBMS and

the H base. Thanks for watching this video