SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#482
  • NoSQL is highly scalable, and highly available, low cost.
  • No
  • It can’t have constraints, and joints are not supported in NoSQL, however it has higher performance to store and retrieve huge amounts of data.
  • No, NoSQL is good if the relationships between data is not important. In this case we use RDBMS.
1 Like
#483
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High Scalability and high availability
  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?
    Whilst a NoSQL DBMS is not very functional as you can’t have constraints and Joins are not supported, it is the correct DBMS in case you need to store and retrieve a high amount of data and RS between data is not too important
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, it is highly recommended to go for SQL DBMS in this case
1 Like
#484
  1. high performance for large number of key/value paired data. schema can change
  2. no
  3. NoSQL is much more scalable than RDMBS, however, it does not support features such as joins and constraints.
  4. no, NoSQL does not keep track of relationships among the data stored
1 Like
#485 
  1. Some of the advantages of NoSQL are that it is easy to scale, faster than most other databases and it handles large amounts of dat easier than other data bases.

  2.  NoSQL does not require a defined structure.

  3.  Scalability is important where large amounts of data will be processed, it requires a database that is fast in retrieving and processing data.  On the other hand functionality is important where a set format is needed that requires several fields of data to be manipulated, such as in banks.

  4.  No NoSQL is not the best choice.
1 Like
#486

.)What are some of the advantages of NoSQL databases compared to SQL databases?
A.) One of the advantage of NoSQL database is that they are really easy to scale and they are much faster in most types of operations that we perform on database. (high scaleability, high availability AND FAST.)
2.) Do you have to defined a strict structure for your data in NoSQL?
A.) A STTRICT STRUCTURE IS NOT NEED BUT A GOOD STRUCTURE ALWAYS HELPS.
NoSQL (Not SQL or Not Only SQL) is a generic term used for databases that do not depend on a relational model. The data does not need to have a strict schema nor the usual SQL table structure. Most commonly, the data is aggregated as key-value pairs, JSON documents, graphs, or wide-column tables.
3.) What can you say about the trade-off between scalability and functionality in NoSQL?
A.) SECURITY IS NUMBER 1 IN MY OPINION. iTS A MASSIVE TRADE OFF.
4.) If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?

A.)NO IT IS A BAD IDEA IF RELATIONSHIPS ARE NEEDED. USE RDMS, WHEN RELATIONSHIPS ARE NEEDED. SQL WAS CREATED FOR THIS PURPOSE AND IS ALSO MORE SECURE.

1 Like
#487

  • What are some of the advantages of NoSQL databases compared to SQL databases?
    Faster to use and easier to scale, not very expensive, uses that are not for relationship.

  • 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?
    Since this database doesn’t have a big need or focus on relationships, and needs to focus more on speed of getting data to be received and stored it is worth it.

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

1 Like
#488

  1. Main advantages of NoSQL are horizontal scalability and performance.

  2. No, the structure can be modified on the fly to a certain extent of course.

  3. NoSQL DBs have biggest advantage in terms of scalability and disanvatage in terms of functionalities compared to SQL like JOIN. However, functionalities could be brought back on application level in NoSQL, while you cannot do the same with scalability on SQL DB.

  4. No, that would not be a good idea, however, not impossible.

2 Likes
#489
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

high scalability and high availability

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

No

  1. What can you say about the trade-off between scalability and functionality in NoSQL?

Joins and Adding constraints or structure to the data for functionality, one must happen at the Application level rather at the database level to maintain the database’s saleability and performance

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

No

1 Like
#490

1.scalability and performance
2. no, you can insert and update on the fly
3. if you have huge amount of data which is growing will be a good trade off because you need high scalability to handle that data in efficient manner
4. not really , it´s better to chose RDBMS database which has more functionality for important relationships

1 Like
#491
  1. High Scalability (sharding) + High Availability (replication)
  2. No
  3. You’d have to choose based on your application. If it’s about storing large amounts of data that doesn’t require joining, go with NoSQL.
  4. No
1 Like
#492

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

  • High Scalability & High Availability
    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?**
  • NoSQL is easily scaled
  • NoSQL handels common operations faster than SQL
  • NoSQL is good for horizontal scaling which is easier to implement than vertical scaling
    4.If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?**
    NO…SQL is best for relationships.
1 Like
#493

  1. for sql when file is sent it has to fully be 100% transfer or it doesnt save at all in case for for example a power outage, power goes out while doing a trade sql wont save something thats 30% complete it will lose that information. With NoSQL on the other hand it saves as much data as you put through even through the case of the power outage so, Auto replication feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state.

  2. no

  3. not good if data is important, structured and changing over time. good if you want to store and retrieve huge amount of data, and data that is growing continuously and you need to scale the database regular to handle the data.

  4. no, its is better to use a rdbms because it is relational.

1 Like
#494
  • What are some of the advantages of NoSQL databases compared to SQL databases?
    A: Highly scalable, data can be inserted and updated on the fly, good for huge amounts of data.
  • Do you have to defined a strict structure for your data in NoSQL?
    A: NO
  • What can you say about the trade-off between scalability and functionality in NoSQL?
    A: It is a business decision that needs to be made by the designers based on use case for the system. If the data is not highly relational and scalability is desired, then a NoSQL DB is the better option.
  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    A: NO
1 Like
#495
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The two main advantages are the high scalability and the high availability.
  2. Do you have to defined a strict structure for your data in NoSQL?
    No. Data is stored in JSON(for example). With NoSQL you cannot perform CRUD though.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    With NoSQL, you can’t use constraints or joints. Which makes NoSQL more scalable but in counter is it less functional to use then SQL.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No! You need to use SQL to store datas that have relationships!
1 Like
#496
  1. Better performance for vast amounts of data. Data stored in JSON - the same format as most apps that communicate with database. You don’t have to define and redefine models and schemas each if data structure changes.
  2. NO, you can load data right away.
  3. NoSQL provides less functionality but more scalability. It’s better for some purposes, such as storing live data about weather conditions or currency rates, for example.
  4. In cases when you need to understand data relations, NoSQL would not be a good choice because of the lack of functionality and no defined relations between data.
1 Like
#497

NoSQL uses sharding methods which allows more scalability and it also provides recovery of data.

No because it is easier to update compared to SQL.

As scalability increases, functionality decreases.

No

1 Like
#498

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL is highly scalable so if you have very large data sets of key value pairs where structure is not required outside the pair then NoSQL provides is more efficient and less overhead.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No NoSQL does not require a schema which is a benefit depending upon the use case.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL scales great but you don’t have relational keys so functionality suffers so it depends upon your use case as to whether it is an appropriate solution.

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

1 Like
#499

1.Higher Performance is probably the most significant. Another advantage is that it can handle high load of consistent changing of data

2.No you do not - Although some NoSQL can have some structuring. Most of its functionality is at the “application level”

3.Scalability is what you gain for “giving up” functionality. In the case of NoSQL, constraints (complexity) and joins hinder its performance meaning it is less structured but faster at what its specifically built for (lots of data at a quicker rate)

4.In this case no, you would be a bit better and much more efficient with a SQL database

1 Like
#500
  1. More scalable.
  2. No
  3. NoSQL can handle bigger amounts of data and run operations faster while it’s not as safe as an SQL and it can’t run as complex operations as SQL.
  4. No
1 Like
#501
  1. NoSQL can handle a larger amount of data more efficiently than SQL,
  2. No there is not structure to the data
  3. You lose joins and search-ability functions but gain in speed and scaling.
  4. No if you want to maintain relationships use a SQL database.
2 Likes