filmov
tv
How to choose RIGHT DATABASE ? | Type of Database | Code Decode | System Design Interview Question
Показать описание
In this video of code decode we have explained best database to choose from. This is very Important Interview questions with respect to System Design
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
Scenarios where we need to choose between NOSQL DB and relational DBs ?
Scenario 1: READ Vs WRITE Intensive Application
When your application is read intensive the use NOSQL db .
If the application is Write Intensive then go for Relational DB.
Why ? If we have to read a lot and update less, then having multiple relational DBs and having join queries to read a lot of data base will decrease the performance. So better go with Non relational DBs. Now everything will be in one document and no joins, views complex queries wool be required which decreases the readability, performance , speed and other non functional parameters of aplication
Scenario 2: Unstructured VS Structured Data
When your application is going to persist the data which is not structured, there is no guarantee on how many fields we will get and we need to store then its unstructured data. Then go for No sql DB choice as there is no restriction on columns or fields in which data has to be inserted .
But If we are very sure the data structure wont change ever in whole life cycle of application then even relational DB is also a good choice
Scenario 3: Concurrency and atomicity is top priority
In applications like hotel / movie ticket booking - Several users simultaneously read and write the data.
To prevent data inconsistency, such as the double booking of hotel rooms, we must coordinate such transactions.
Transactional access to the data in a relational database manages concurrency.
A transaction is regarded as an atomic operation, making it possible to roll back or commit a transaction after a successful execution in error handling.
To facilitate this feature we need Relational Dbs .
Scenario 4: Cost associated
If we are allotted a very less budget for the project, go for open source NO Sql db as many NoSQL databases are open source and freely available..
While with Relational DBs, these are not open source usually n we need to purchase the License for it.
Hibernate Interview Questions and Answers:
Spring Boot Interview Questions and Answers:
Subscriber and Follow Code Decode
#dsa #leetcode #codedecode
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
Scenarios where we need to choose between NOSQL DB and relational DBs ?
Scenario 1: READ Vs WRITE Intensive Application
When your application is read intensive the use NOSQL db .
If the application is Write Intensive then go for Relational DB.
Why ? If we have to read a lot and update less, then having multiple relational DBs and having join queries to read a lot of data base will decrease the performance. So better go with Non relational DBs. Now everything will be in one document and no joins, views complex queries wool be required which decreases the readability, performance , speed and other non functional parameters of aplication
Scenario 2: Unstructured VS Structured Data
When your application is going to persist the data which is not structured, there is no guarantee on how many fields we will get and we need to store then its unstructured data. Then go for No sql DB choice as there is no restriction on columns or fields in which data has to be inserted .
But If we are very sure the data structure wont change ever in whole life cycle of application then even relational DB is also a good choice
Scenario 3: Concurrency and atomicity is top priority
In applications like hotel / movie ticket booking - Several users simultaneously read and write the data.
To prevent data inconsistency, such as the double booking of hotel rooms, we must coordinate such transactions.
Transactional access to the data in a relational database manages concurrency.
A transaction is regarded as an atomic operation, making it possible to roll back or commit a transaction after a successful execution in error handling.
To facilitate this feature we need Relational Dbs .
Scenario 4: Cost associated
If we are allotted a very less budget for the project, go for open source NO Sql db as many NoSQL databases are open source and freely available..
While with Relational DBs, these are not open source usually n we need to purchase the License for it.
Hibernate Interview Questions and Answers:
Spring Boot Interview Questions and Answers:
Subscriber and Follow Code Decode
#dsa #leetcode #codedecode
Комментарии