From 00b963066949c84bb5f0f2636e14d4221653864b Mon Sep 17 00:00:00 2001 From: Muhammad Khalid <52286894+theMuhammadKhalid@users.noreply.github.com> Date: Sun, 31 Dec 2023 06:24:07 +0500 Subject: [PATCH] typo: `followinw` to `following` (#4943) --- .../system-design/content/111-databases/102-sql-vs-nosql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/data/roadmaps/system-design/content/111-databases/102-sql-vs-nosql.md b/src/data/roadmaps/system-design/content/111-databases/102-sql-vs-nosql.md index f0dd33516..0dc25dbf8 100644 --- a/src/data/roadmaps/system-design/content/111-databases/102-sql-vs-nosql.md +++ b/src/data/roadmaps/system-design/content/111-databases/102-sql-vs-nosql.md @@ -6,7 +6,7 @@ NoSQL databases, such as MongoDB and Cassandra, are best suited for unstructured The choice between SQL and NoSQL depends on the specific use case and requirements of the project. If you need to store and query structured data with complex relationships, an SQL database is likely a better choice. If you need to store and query large amounts of unstructured data with high scalability and performance, a NoSQL database may be a better choice. -Learn more from the followinw links: +Learn more from the following links: - [SQL vs NoSQL: The Differences](https://www.sitepoint.com/sql-vs-nosql-differences/) - [SQL vs NoSQL - When to Use Each](https://www.ibm.com/cloud/blog/sql-vs-nosql)