Disadvantages of RDBMS or RDBMS vs NoSQL
I will present my vision for what reasons new data storage and processing technologies known as NoSQL and MPP were created.
The article will be useful especially for novice pioneers in the development of the database.
The article does not consider specialized databases for vector, graphic and other non-standard formats.
First, SQL and RDBMS
1.1. You need to know the SQL language and the basic principles of RDBMS as a transaction, foreign key, table.
Suppose you are a Java developer, and you are still required to know some kind of SQL and features of RDBMS. Naturally you are lazy, trying to somehow sabotage.
And besides, the principle of OOP is not very similar to the data model in the RDBMS.
1.2. If you have a large project, then you need a professional DB developer, and this is an extra ballast if there are no projects in the future.
Java programmers want to do all Java business logic bypassing SQL and RDBMS.
Second, Price
2.1. The inability to use the commodity server on big data. If you have 600 Terabytes, then only Exadata or Teradata will suit you from RDBMS.
2.2. Fault tolerance. Without shared-nothing and no single point failer technology, you have to buy expensive servers, with double redundancy of everything,
RAID controllers, power supplies, buy bespereboynik, expensive storage and so on.
2.3. Price license. Advanced capabilities RDBMS capable of keeping hundreds of terabytes is not cheap, especially appliance solutions.
')
Third,> = 1 Pb data
3.1. If you have more than 1 Petabyte of data, then only Teradata for $ 20 million is suitable for you from the RDBMS
Then how to build a cluster for Hadoop with triple redundancy on 1 Petabyte of data now costs $ 367,000 (only servers with disks).
On such servers and 4 disks in RAID 0
www.ulmart.ru/goods/613438
www.ulmart.ru/goods/690535
Truth on electricity go broke. For such a child will need a mini power plant.
That's actually the reason why this NoSQL, Hadoop, MPP movement began. To solve the above features, inconvenience, disadvantages.
Conclusion:
RDBMS still remain universal databases capable of solving any problems. So I advise you once again to think whether one of the above points is critical for you . If not, feel free to take a regular RDBMS!
Verdict:
1. If you have money, chickens don’t bite, you have complicated development or you need non-blocking reading and you like comfortable development conditions.
Buy Exadata
2. If you have money, chickens do not peck, not very difficult development, you are not afraid of the lack of good tools,
and you do not like to create units, but you like the brute force of full scan then buy Teradatu
3. If you have money, but you know how to count it, you need a stable, versatile and easy to develop database and data, you have less than 10 terabytes, and you are not afraid of the complexity of administration, then take a regular Oracle
4. If you do not have money, but data is no more than 1 TB, but you still need a good platform for developing a database with complex logic, then take PostgreSQL
5. If you do not have SQL and RDBMS skills, the data is loosely coupled or you have a good ETL that catches everything. Not complex queries without joining multiple tables. All logic is not in the database. NoSQL DB is quite suitable for you, although, as I said, RDBMS are universal, anything can do if you know how to use them.
The article will be useful especially for novice pioneers in the development of the database.
The article does not consider specialized databases for vector, graphic and other non-standard formats.
First, SQL and RDBMS
1.1. You need to know the SQL language and the basic principles of RDBMS as a transaction, foreign key, table.
Suppose you are a Java developer, and you are still required to know some kind of SQL and features of RDBMS. Naturally you are lazy, trying to somehow sabotage.
And besides, the principle of OOP is not very similar to the data model in the RDBMS.
1.2. If you have a large project, then you need a professional DB developer, and this is an extra ballast if there are no projects in the future.
Java programmers want to do all Java business logic bypassing SQL and RDBMS.
Second, Price
2.1. The inability to use the commodity server on big data. If you have 600 Terabytes, then only Exadata or Teradata will suit you from RDBMS.
2.2. Fault tolerance. Without shared-nothing and no single point failer technology, you have to buy expensive servers, with double redundancy of everything,
RAID controllers, power supplies, buy bespereboynik, expensive storage and so on.
2.3. Price license. Advanced capabilities RDBMS capable of keeping hundreds of terabytes is not cheap, especially appliance solutions.
')
Third,> = 1 Pb data
3.1. If you have more than 1 Petabyte of data, then only Teradata for $ 20 million is suitable for you from the RDBMS
Then how to build a cluster for Hadoop with triple redundancy on 1 Petabyte of data now costs $ 367,000 (only servers with disks).
On such servers and 4 disks in RAID 0
www.ulmart.ru/goods/613438
www.ulmart.ru/goods/690535
Truth on electricity go broke. For such a child will need a mini power plant.
That's actually the reason why this NoSQL, Hadoop, MPP movement began. To solve the above features, inconvenience, disadvantages.
Conclusion:
RDBMS still remain universal databases capable of solving any problems. So I advise you once again to think whether one of the above points is critical for you . If not, feel free to take a regular RDBMS!
Verdict:
1. If you have money, chickens don’t bite, you have complicated development or you need non-blocking reading and you like comfortable development conditions.
Buy Exadata
2. If you have money, chickens do not peck, not very difficult development, you are not afraid of the lack of good tools,
and you do not like to create units, but you like the brute force of full scan then buy Teradatu
3. If you have money, but you know how to count it, you need a stable, versatile and easy to develop database and data, you have less than 10 terabytes, and you are not afraid of the complexity of administration, then take a regular Oracle
4. If you do not have money, but data is no more than 1 TB, but you still need a good platform for developing a database with complex logic, then take PostgreSQL
5. If you do not have SQL and RDBMS skills, the data is loosely coupled or you have a good ETL that catches everything. Not complex queries without joining multiple tables. All logic is not in the database. NoSQL DB is quite suitable for you, although, as I said, RDBMS are universal, anything can do if you know how to use them.
Source: https://habr.com/ru/post/236523/
All Articles