Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| arch:can_rdbms_scale_under_load [2021/12/19 20:40] – created dakireev | arch:can_rdbms_scale_under_load [2026/08/29 07:59] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Can RDBMS scale under load? A survey of the case studies | + | ==== Can RDBMS scale under load? A survey of the case studies |
| Relational databases first appeared in 1970 and have been evolving ever since. Nevertheless, | Relational databases first appeared in 1970 and have been evolving ever since. Nevertheless, | ||
| Line 6: | Line 6: | ||
| It is important to note that there are two types of scaling: vertical and horizontal [1]. | It is important to note that there are two types of scaling: vertical and horizontal [1]. | ||
| - | Vertical scaling, or "scale up", is achieved by increasing the capabilities of one node, for example, by upgrading CPU, adding memory or storage. | + | Vertical scaling, or “scale up”, is achieved by increasing the capabilities of one node, for example, by upgrading CPU, adding memory or storage. |
| - | Horizontal scaling, or "scale out", is achieved by increasing amount of nodes in the cluster. This type of scaling requires many issues, like resource management, task allocation, and latency. However, this type of scaling has virtually no limit and is how most large-scale applications exist, like social networks. | + | Horizontal scaling, or “scale out”, is achieved by increasing amount of nodes in the cluster. This type of scaling requires many issues, like resource management, task allocation, and latency. However, this type of scaling has virtually no limit and is how most large-scale applications exist, like social networks. |
| However, due to their core design originating in 1970, they were not meant for scaling, especially horizontal. There are some solutions, but it is still a common problem. This does not stop them from scaling vertically: better storage, memory, and processors do increase their performance. Even one of the popular RDBMS, MariaDB, only differs from another, more popular RDBMS, MySQL, in the way it stores data. | However, due to their core design originating in 1970, they were not meant for scaling, especially horizontal. There are some solutions, but it is still a common problem. This does not stop them from scaling vertically: better storage, memory, and processors do increase their performance. Even one of the popular RDBMS, MariaDB, only differs from another, more popular RDBMS, MySQL, in the way it stores data. | ||
| Line 15: | Line 15: | ||
| To sum up all of the mentioned above, it's clear that traditional RDBMS can't scale enough under a high load. They can scale vertically, but they have their limits and is insufficient for high load computing | To sum up all of the mentioned above, it's clear that traditional RDBMS can't scale enough under a high load. They can scale vertically, but they have their limits and is insufficient for high load computing | ||
| - | Literature: | + | === References === |
| - | https:// | + | |
| - | https:// | + | |
| - | Hadjigeorgiou, | + | |
| - | Hollingsworth, | + | |
| - | Kumar, R., & Charu, S. (2014). Newsql databases: Scalable rdbms for oltp needs to handle big data. International Journal of Modern Computer Science (IJMCS), 3, 13-17. | + | |
| + | - [[wp> | ||
| + | - [[wp> | ||
| + | - Hadjigeorgiou, | ||
| + | - Hollingsworth, | ||
| + | - Kumar, R., & Charu, S. (2014). Newsql databases: Scalable rdbms for oltp needs to handle big data. International Journal of Modern Computer Science (IJMCS), 3, 13-17. | ||