Relational vs Non-Relational Databases.
| S.No | Relational Database | Non-Relational Database |
| 1 | It was introduced in the 1970s. | It was introduced in the 1960s. |
| 2 | They are popularly known as SQL Databases. | They are commonly known as NoSQL Databases. |
| 3 | Data is stored in tables (in the form of rows and columns). | Data is either structured or unstructured. |
| 4 | It is probably going to have a larger server to accommodate a lot of amount of data. | In NoSQL databases, we don’t have to buy a larger server to manage data, rather they can scale horizontally(can add new servers to what you already have as needed). |
| 5 | Vertically Scalable. | Horizontally scalable. |
| 6 | Slower to access the data. | Quite faster than a relational database to access the data. |
| 7 | These databases have fixed or static or predefined schema. | They have a dynamic schema. |
| 8 | These databases are not suited for hierarchical data storage. | These databases are best suited for hierarchical data storage. |
| 9 | Follows ACID property. | Follows CAP(consistency, availability, partition tolerance). |
| 10 | These databases are best suited for complex queries | These databases are not so good for complex queries |
| 11 | For example: MySQL, Oracle, MariaDB, SQLite, etc. | For example MongoDB, Neo4j, Redis, etc. |
