SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#582

  1. Advantages of NoSQL over SQL:
    – high scalability
    – high performance
    – storage in JSON format available

  2. There is no need to define a strict structure for your data

  3. In order to provide higher scalability, NoSQL offers less functionality

  4. NoSQL is not a good choice if you need to keep track of important relationships in your data

2 Likes
#583
  1. What are some of the advantages of NoSQL databases compared to SQL databases? a NoSQL database is more easily scalable, requires less processing power - faster, you dont have a pre-defined schema for what data needs to be saved.
  2. Do you have to defined a strict structure for your data in NoSQL? No, the structure of the data can change over time and as needed.
  3. What can you say about the trade-off between scalability and functionality in NoSQL? Wile NoSQL is more scalable, it has less functionality, in the sense that you cannot store relationships between data points within the database.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No, an SQL database should be used which can store the relationships.
1 Like
#584

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Low cost, speed and scalability.

  2. Do you have to defined a strict structure for your data in NoSQL?
    Nou you don’t.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL can handle large volumes of data so it scales easily but it comes with less functionality.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    Nope. In that case it’s best to go with RDBMS.

1 Like
#585
  1. In a traditional SQL database you are required to create the table define the schema, set the data types of fields et. before you can actually input the data. In a NoSQL database you simply insert and update as you go.
  2. You do not need to define a strict structure for data in NoSQL.
  3. NoSQL is more scalable because it uses horizontal scaling rather than vertical making it easier to scale. It is however less functional because constraints and joints are not supported.
  4. If you need to track relationships in your database you need to you SQL because NoSQL doesn’t support relationships.
3 Likes
#586
  1. High scalability and high availability
  2. No
  3. High performance.
  4. No, you should use SQL instead.
2 Likes
#587
  1. Don’t have to create tables and define schema, also they are easy to scale and are usually faster.
  2. No
  3. With the more scalability the functionality is more relied on through the application level
  4. No you would want to use SQL
2 Likes
#588
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL databases have a better performance than SQL when processing huge amounts of data, and when managing semi-structured data (or data that changes its structure frequently). They also have high scalability and availability .
  2. Do you have to defined a strict structure for your data in NoSQL?
    No, you don’t need to define any data structure in NoSQL. In SQL you must do it before using the data.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    The key factor is relationship enforcement, as it gives you the chance to run complex operations and to preserve data integrity at the cost of a slower performance and a previously-defined structure.
    So, if you have relationship enforcement, like in SQL, you will be able native support to run queries based on those relationships (which represents more functionality). In NoSQL you must implement this logic in the server-side application. If you don’t enforce those rules, your performance and scalability will be improved, as you won’t have restrictions over the data, and you will be able to implement sharding (which would be difficult if you need to check constraints).
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, because it has not native support for relationships. In this case SQL would be a better call.
2 Likes
#589
  1. NoSQL offers high scalability and high availability by storing data in hierarchical structures. SQL has direct mapping to the 4 actions - create, select, update, delete - by stitching/reassembling tables of data together.
  2. No, data is not defined with structure in NoSQL, you can insert and update data on the fly.
  3. Having clarity on your use-case and growth potential will offer insight on priorities for your development - will scalability or functionality rule? If growth is priority, then scalability will rule. If relationships are integral for your use-case, then functionality is likely your priority.
  4. NoSQL would not be ideal for developments that prioritize relationships.
2 Likes
#590

  1. With no Sql you can do alot more.

  2. No, it’s more malleable.

  3. Depends on the need.

  4. No, SQL is better.

2 Likes
#591

  • What are some of the advantages of NoSQL databases compared to SQL databases?
    -> Easily scalable and not strongly structured

  • Do you have to defined a strict structure for your data in NoSQL?
    -> No

  • What can you say about the trade-off between scalability and functionality in NoSQL?
    -> NoSql are good with scalabiity and performance but constraints and joins are not supported.

  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    -> No

1 Like
#592

( 1.) What are some of the advantages of NoSQL databases compared to SQL databases?

Biggest difference would be security and that SQL is used for relational databases and that NoSQL is used for non-relational or distributed data bases

( 2.) Do you have to defined a strict structure for your data in NoSQL?

No

[ 3. ] What can you say about the trade-off between scalability and functionality in NoSQL?
it is cheaper to scale horizontally but is not good at handling complex quires

( 4.) If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?

No - sensoray data that is chanfes all the time is better suited for this structure

1 Like
#593
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    It’s good to have a NoSQL database when it comes to scaling and storing non-relational data.
  2. Do you have to defined a strict structure for your data in NoSQL?
    No, there’s is no such structure.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    It is less functional but at the same time better for scaling.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, you should then use SQL databases.
1 Like
#594

What are some of the advantages of NoSQL databases compared to SQL databases?
High scalability: NoSQL database such as MongoDB uses sharding for horizontal scaling. Sharding is partitioning of data and placing it on multiple machines in such a way that the order of the data is preserved. Vertical scaling means adding more resources to the existing machine while horizontal scaling means adding more machines to handle the data. Vertical scaling is not that easy to implement, on the other hand horizontal scaling is easy to implement. Horizontal scaling database examples: MongoDB, Cassandra etc. Because of this feature NoSQL can handle huge amount of data, as the data grows NoSQL scale itself to handle that data in efficient manner.
High Availability: Auto replication feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state.
Do you have to defined a strict structure for your data in NoSQL?
No

What can you say about the trade-off between scalability and functionality in NoSQL?
RDBMS: It is a structured data that provides more functionality but gives less performance.
NoSQL: Structured or semi structured data, less functionality and high performance.

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No.

1 Like
#595
  • What are some of the advantages of NoSQL databases compared to SQL databases?
    No SQL database is easier to scale, much faster and more efficient when dealing with large amount of data
  • Do you have to defined a strict structure for your data in NoSQL?
    No
  • What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL database doesn’t have constraint and joins making it more scalable but less functional
  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, if the data has important relationship data, it is better to use SQL
    [/quote]
1 Like
#596
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    you can insert and update data on the fly. they are easier to scale and faster in performing most operations.
  2. Do you have to defined a strict structure for your data in NoSQL?
    it can be structured or semi- structured
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    it is easier to scale thanks to the horizontal scaling solutions but has less functionality
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    no, in this instance you would rather use a relational database
1 Like
#597

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    It’s more scalable, more cost-efficient in its setup, it’s faster and handle large amounts of data.

  2. Do you have to defined a strict structure for your data in NoSQL?
    Nope.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    It takes sacrifices in security in exchange for scalability and speed. NoSQL would not be great for banking, but perhaps vast amounts of weather data.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No.

1 Like
#598
  1. It is RDBMS Vs NoSQL.

RDBMS = It is a structured data provides more functionality but gives less performance

NoSQL = Structured or semi structured data, less functionality and high performance

  1. No, structured or semi structured data.

  2. Joins are not supported in NoSQL, so, these supports actually hinders the scalability of a database, so while using NoSQL database like MongoDB, you can implements these functionalities at the application level.

  3. Nope!

1 Like
#599
  1. NoSQL can scale easier by just adding machines and it is more comparable to the more widespread JSON environments.
  2. No structure can be changed and relationships do not need to be decided
  3. SQL has functionality of relationships built into the code instead of NoSQL where that relationship code for an app needs to be written on top. SQL is also atomic
  4. No unless you feel like writing it into the code.
1 Like
#600
  1. High scalability and high availability
  2. No
  3. Higher scalability takes away a portion of functionality; NoSQLs wouldn’t be good to be used in the banking system
  4. No, because it can not handle important relationships
1 Like
#601
  1. High scalability and high availability
  2. No, you do not have to worry about that, you can insert, update data on the fly.
    3.Higher scalability takes away a portion of functionality; NoSQL wouldn’t be good to be used in the banking system
    4.No, in this case you better use SQL
1 Like