SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#221

Excellent answer sir! really well documented! keep it like that please! :muscle:

Carlos Z.

#222

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Scalability (horizontal), availability, no structure required, faster,

  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?
    You can’t have constraints in NoSQL.
    Joins are not supported in NoSQL.

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

Excellent answer sir! really well documented! keep it like that please! :muscle:

Carlos Z.

#224

  1. scaling especially horizontal scaling, fast, huge data amounts possible,
    high availability due to auto replication to last functional/consistent state

  2. No, data don’t need to be structured.

  3. due to less funtionality NoSQL is more scalable compared to a highly functional but slow and less performant RDBMS.

  4. No, if you need to take care of data-relationships, then RDBMS would be the better choice.

1 Like
#225

1)easy to scale and much faster, best when dealing with huge amount of data, high scalability and high availability
2) no
3)Structured data that gives more functionality gives less performance, when less structured data is needed noSQL is better
4) no

1 Like
#226

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    It is more scalable and faster than SQL

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, it can be changing over time

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    A NoSQL database has reduced functionality compared to an SQL database, e.g. it does not support highly structured data, relationships or joins, however this also makes it a more scalable solution

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

1 Like
#227

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    -don’t need predetermined tables, schema, and data fields - you can insert data on the fly
    -scalability and better for large amounts of data
    -faster for most operations of the database

  2. Do you have to defined a strict structure for your data in NoSQL?
    no. you can adjust and insert on the fly

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    If you need to store and retrieve a huge amount of data, you should go with NoSQL. On the other hand, the noSQL will have reduced functionality such as not being able to utilize constraints and joins.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    no, SQL or another RDBMS would be preferred.

2 Likes
#228
  1. Some advantages of NoSQL databases compared to SQL databases are:

  • Handles a lot of data very quickly (Big Data)

  • Flexible data model with no pre-defined schema (tables, columns, etc.)

  • The data structure allows for handling data that is unstructured.

  • Horizontal scaling out versus up in a relational database - You can use cheaper hardware and add additional nodes to expand your memory if you max things out versus paying for a whole new infrastructure with vertical scaling. “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
this feature can handle a huge amount of data, as the data grows NoSQL scale itself to handle that data in an efficient manner.”

  • According to the reading: High Availability - The Auto replication feature in an unstructured database like MongoDB makes NoSQL “highly available” because in case of any failure data replicates itself to the previous consistent state.

  1. NoSQL is by definition an unstructured database, so you do not necessarily have to define a strict structure for the data. “In relational databases, you need to create the table, define the schema, set the data types of fields, etc before you can actually insert the data. In NoSQL you don’t have to worry about that, you can insert, update data on the fly.”

  2. According to the reading, the trade-off between scalability and functionality in NoSQL vs. RDBMS:
    RDBMS: Structured data that provides more functionality but gives less performance.
    NoSQL: Structured or semi-structured data, less functionality, and high performance.

  • Less functionality in NoSQL means that there are no “constraints” and “JOINS” are not supported in NoSQL. The high performance comes in when you want to store and retrieve huge amounts of data that is continuously growing and changing over time. Scalability is the biggest performance aspect.
  1. A relational database is best if your data has important relationships that you need to keep track of and maintain. NoSQL is the wrong option for this use-case
1 Like
#229

Excellent answer sir! really well documented! keep it like that please! :muscle:

Carlos Z.

#230
  1. Scalability, faster (performance).
  2. No need
  3. Performance.
  4. No, use RDBMS instead
1 Like
#231
  1. really easy to scale and they are much faster in most types of operations that we perform on database.
  2. No, this is one of the perks of NoSQL
  3. Less security, but for streams of data that means a little loss of data is not that bad compared to the unability to receive and store data.
  4. No, with relations it is better to use SQL
1 Like
#232
  1. High scalability, high availability
  2. No
  3. NoSQL is more scalable compared to RDBMS but it comes with less functionality.
  4. No, it is better to use RDBMS
1 Like
#233
  1. Easy to scale and much faster.
  2. No you can insert and update data on the fly
  3. Scalability is much better due to i.e. horizontal and vertical sharding. However you cant have constraints in NoSQL and joins are not supported.
  4. No in that case you are better of with a relational database.
1 Like
#234
  1. Scalable do to sharding functionality and can easily handle large amounts of data
  2. No contraints with NoSQL but the data structure needs to be fixed
  3. It depends on what you are ultimately trying to achieve, but if there are no relationships of the data needed and coinstraint and join functions arent required at the database level you are good to go, if relationships exist and you need to change the data structure is dynamic mysql or orther is the way to go. NoSQL is highly scalable, great performance, and has high availability, the trade off is functionality.
  4. No go with MySQL or other.
1 Like
#235

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    -easier to scale
    -high availability
    -much faster in certain operations than on SQL databases
    -does well with large amounts of data
    -store their data in JSON format

  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 has less functionality but is more scalable and better performance.

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

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL is scalable while SQL not so much. Scalability in NoSQL uses horizontal sharding which is comparatively inexpensive to SQL’s vertical scaling.

  2. Do you have to defined a strict structure for your data in NoSQL?
    There is no defined structure to NoSQL making it less functional.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Chose NoSQL if you need to scale ever changing data and don’t need it to be relational.

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

1 Like
#237
  1. High scalability, high availability
  2. No
  3. Structured or semi structured data, less functionality and high performance.
  4. No.
1 Like
#238

1) The main advantages are high scalability and high availability.
2) In NoSQL you don’t have to worry about that, you can insert, update data on the fly.
3) NoSQL has higher scalability but less functionality. If you need a database that dont require much functionality and fast scaling than it is worthy trade off.
4) No

1 Like
#239
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Data can be inserted on the fly, low cost, easy scalability.
  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?
    If you need to add large amounts of data and scale NoSQL works better but at the cost of functionality.
  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 not.
2 Likes
#240
  • What are some of the advantages of NoSQL databases compared to SQL databases?

NoSQL advantage
Scalability
Low cost

SQL
Speed
Support joins, relations

  • **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 is better supporting scalability than functionality.

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

1 Like