{"componentChunkName":"component---src-templates-blog-post-js","path":"/development/sql-vs-nosql--which-one-you-might-want-to-use/","webpackCompilationHash":"f92dbf25810602c1889e","result":{"data":{"site":{"siteMetadata":{"title":"Web Devlog","author":"RossenaHuh","siteUrl":"https://github.com/rossenahuh","comment":{"disqusShortName":"RossenaHuh","utterances":"rossenahuh/my-dev-blog.git"},"sponsor":{"buyMeACoffeeId":"rossena"}}},"markdownRemark":{"id":"3df898c9-e2aa-57e4-beff-43116bc92963","excerpt":"What is SQL?Structured Query Language with which you can retrieve/insert/update/delete the data you need from database.Relational DatabaseA database which works with certain assumptions or in a certain way and it supports the sql. Such database works with tables. Have to be…","html":"

What is SQL?

\n

Structured Query Language with which you can retrieve/insert/update/delete the data you need from database.

\n

Relational Database

\n

A database which works with certain assumptions or in a certain way and it supports the sql. Such database works with tables. Have to be precise with a clear schema of which data can go into a table which has own fields(columns) and records(rows). It can’t hold more fields than the ones we defined for the table.\nAll records have to follow this schema. You typically don’t only work with one table but instead with multiple tables which are related.

\n

Non Relational Database

\n

In Non Relational Database, there’s no schema applied therefore you can be more flexible regarding the data format. Generally there are no relations in no sql world. Putting all the information in one place. Have less relation merging going on, have super fast end efficient queries therefore. But the disadvantages is that you have some duplicates in data.

\n

Then which one is a winner?

\n

There’s no clear winner. It really depends on the kind of application you are building and the kind of data you are storing. With really big applications or businesses you typically use both.

\n
\n

SQL

\n\n
\n

NoSQL

\n\n
\n

SQL will be a better choice for the business that has pre-defined structures such as accounting system, inventory monitoring system or when running on legacy systems.

\n
\n

NoSQL will be a strong choice for any businesses that have rapid growth, no clear definition for schema or when the schema continues to change in cases like real-time analytics or content management systems.

\n
\n
\n

sorces

\n

https://www.xplenty.com/blog/the-sql-vs-nosql-difference/?source=post_page---------------------------\nhttps://www.youtube.com/watch?v=ZS_kXvOeQ5Y&t=1121s

\n
\n
","frontmatter":{"title":"SQL vs NoSQL- Which one you might want to use","date":"July 18, 2019"}}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"/development/sql-vs-nosql--which-one-you-might-want-to-use/","previous":{"fields":{"slug":"/development/what-are-cicd-and-devops/"},"frontmatter":{"title":"What are Agile, DevOps and CICD","category":"Development"}},"next":{"fields":{"slug":"/React/react-concept-1---virtual-dom/"},"frontmatter":{"title":"React Concept 1 - Virtual DOM and the myths around it solved","category":"React"}}}}}