NoSQL: El Otro Tipo de Bases de Datos

The shift by tech giants such as Meta, Twitter and Adobe from SQL to non-SQL databases marked a significant trend in technology. Companies such as Uber, Netflix and Google have also adopted non-SQL due to the need to adapt quickly to changes in data usage.

The flexibility of no SQL is crucial for startups, allowing value to be added in every sprint. Non-SQL does not imply the total exclusion of the SQL language; there are non-SQL databases that also support SQL. This term became popular in the 2000s because of the need to handle data differently as the cost of storage decreased and applications needed to store and query more data.

What is not SQL?

• SQL, which stands for Structured Query Language, is a standard language used in many database technologies.
• Non-SQL does not necessarily mean not using SQL; some non-SQL databases support SQL.
• Originally, no SQL was associated with non-relational databases, but today it has a broader meaning.

Why did the need for no SQL arise?

• Non-relational databases have been around since the late 1960s.
• In the 2000s, the need to handle large volumes of data and the reduction in storage cost drove the adoption of non-SQL.
• Non-SQL allows structured, semi-structured and polymorphic data to be stored, offering flexibility and new possibilities.

What are the types of non-SQL databases?

• Network databases.
• Document-based.
• Key-value.
• Columnar.
• Vector.

How do non-SQL databases scale?

• SQL databases scale vertically (more RAM, CPU, storage capacity).
• Non-SQL allows scaling horizontally, facilitating data partitioning through strategies such as sharding.
• This technique distributes data across different clusters, improving read and write efficiency.

What characteristics differentiate non-SQL?

• Focus on consistency, availability and partition tolerance (CAP Theorem).
• Non-SQL databases can fulfill only two of these three characteristics, which represents an advantage depending on the use.
• It is important to know the advantages and disadvantages to choose the best database for each application.

When to use non-SQL databases?

• When flexibility is required to add value quickly in projects with constant changes.
• When handling large volumes of data that need to scale horizontally.
• In applications where consistency and availability are more critical than partition tolerance, or vice versa.