SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#662
  1. They are better when you have to deal with huge amounts of data and the relation among the data is not so important. They are easy to scale, much faster, high availability and highly scalable.
  2. No
    3.Joins or constrains cannot be present, that’s why NoSQL are more flexible and scalable
  3. No, better SQL
1 Like
#663

  1. NoSql Databases scale easier due to having to only worry about large amounts of simple data.

  2. No

  3. It really depends on what your using it for a NoSQL database could be the better option for large simple data. Whereas if you need to know more relational events an SQL database would be more functional.

  4. No its better to use an SQL database for that.

1 Like
#664

  1. The main advantages of NoSQL are scalability and speed.

  2. No.

  3. It all depends on ones needs, if scalability and speed are needed then NoSQL is the one to go for. If relational database is required then SQL would be more suitable.

  4. No, SQL is more suitable.

1 Like
#665
  1. What are some of the advantages of NoSQL databases compared to SQL databases? High scalability, high availability, speed
  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?
    When you want to store and retrieve huge amount of data. The relationship between the data you store is not that important. The data is not structured and changing over time. Constraints and Joins support is not required at database level. The data is growing continuously and you need to scale the database regular to handle the data.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No.
2 Likes
#666
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

Better for performance, scalability and large amounts of data. Also for data that isn’t static, but may change over time.

  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?

You can scale easily, but lack the relational functionality of SQL.

  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
#667

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    No worries regarding the creation of tables, nor defined schemas, and/ or the setting of data types. With NoSQL one can insert and/ or update data on the instantly.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, one does not need to define a strict data structure in NoSQL.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    High scalability; horizontal sharding, in order to preserve data. Less functionality and high performance.

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

Best Regards,

References
Retrieved From: https://beginnersbook.com/2017/09/introduction-to-nosql/

1 Like
#668
  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, it can be updated as you enter data
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    If the relationship b/w the data is not that important AND you have a lot of data than choose NoSQL.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    The limited functionality of NoSQL would not be the best choice for the data.
1 Like
#669

1 - scalable, lower cost, structure easy to change over time,
2 - no
3 - with more functionality and relations there is lower performance. Where large amounts of data need to be stored and retrieved, and scalability and performance are key factors, nosql is better, although less secure.
4 - no

1 Like
#670
  1. Easier to scale. No need to structure and can change over time.
  2. You do not need to have structured data.
  3. Trade offs
  • You cannot have constraints.
  • Joins are not supported.
  • You have less functionality
  1. I f the important functionality needed is relationship between data an SQL DB is preferred.
1 Like
#671

  1. What are some of the advantages of NoSQL databases compared to SQL databases? The main advantages are high scalability and high availability.

  2. Do you have to have a 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? You don’t have to have a defined strict structure and you have better performance, but you have less functionality than RDBMS. Regarding less functionality, you can’t have constraints in NoSQL and joins are not supported. These supports actually hinder scalability, but you can implement the supports at the application level.

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

#672

1.Scalibility and availability
2.not necessarily
3.In order to have scalability, functions such as Joins or constraints cannot be present and that is why NoSQL allows for flexibility in scalability.
4.No. If the data has important relationship it is better to use SQL to manage the relationships.

1 Like
#673

SQL and Relational Databases - Reading Assignment

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • high scalability & high availability
  • no need to create table, define schema, set the data types of fields, etc.
  • you can insert data and just start. it is possible to insert and update data “on the fly”
  • easy to scale and much faster in most types of operations which are performed on a database
  1. Do you have to define a strict structure for your data in NoSQL?
  • no, see answer 1
  1. What can you say about the trade-off between scalability and functionality in NoSQL?
  • NoSQL offers less functionality while it is scalable and high performant
  • as I understood, it is possible to implement the missing functionalities if you need them, but it hinders the scalability of the database / don’t hesitate to correct me if I’m wrong
  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  • it is not a good idea because SQL would be the better choice for relational data.
1 Like
#674
  1. They are really easy to scale and they are much faster in most types of operations.
  2. Nope.
  3. NoSQL is does not have the functionality of RDBMS but is more scalable and higher performance.
  4. No, RDBMS would be better.
1 Like
#675

SQL-DBs are easy to scale, more flexible and much faster, also when dealing with huge amount of data.
2.
No, the structure can be changed over time.
3.
NoSQL: structured or semi structured data, less functionality and high performance.
4.
No, in case where relationships are very important, SQL should be preferred.

1 Like
#676
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

They scale much better
They give better performance
They can handle high volumes of data like data streams

  1. 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?

SQL is more functional but has less performance while No SQL has less functionality but has high performance. As perfromance increase, functionality drops and vica versa.

  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
#677

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

You don’t need to set up the precise structure in advance and they are easy to scale and much faster in most types of operations.

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

No. It is possible to take in vast amounts of unstructured data into NoSQL databases.

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

NoSQL is good for data streams, e.g. AI learning, where the latest and most accurate data is not that important. NoSQL is good for scalability and can handle vast amounts of data and doesn’t require that this data is stricly organised. The trade-off though is that complete accuracy of data cannot be relied on. It would be an extremely bad idea to use NoSQL in air traffic control for example, because knowing the precise accurate location of each plane is critical in that situation. A NoSQL database could potentially give the position of the plane where it was some time ago. NoSQL does not always return the latest information.

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

It may not be a good idea because NoSQL is more appropriate when the relationship between the data that is stored is not so important. You cannot use NoSQL if you need to rely on the accuracy of the data or its relationship to other data.

1 Like
#678

  1. High scalability and high availability.

  2. No.

  3. It can quickly store large amounts of data but suffers a bit in update speeds.

  4. No SQL would be the better choice.

1 Like
#679
  1. Fast, scalable, limited structural setup, lower operational cost,can hold lots of data.
  2. No
  3. NoSQL gives more functionality but less performance.
  4. No
1 Like
#680

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

High Scalability due to sharding and high availability i.e the ability fr data to replicate itself

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

No

3.What can you say about the trade-off between scalability and functionality in NoSQL?
If you need to handle large amounts of data over time then you might elect to do without constraints or JOIN functionality that you would get in a relational database

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No, in that case it would be best to use a relational database

1 Like
#681
  1. high scalability and high availability.
  2. no, In NoSQL you don’t have to worry about that, you can insert, update data on the fly.
    1. You can’t have constraints in NoSQL
  1. Joins are not supported in NoSQL since these supports actually hinders the scalability of a database.but you can do it in an application level.
  1. no you better use SQL
1 Like