SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#241
  1. The advantage of a NoSQL database is clearly scale. If records do not need complex relationships and queries and data is of large volume NoSQL would be the way forward
  2. A strict structure is not needed with NoSQL as one of the advantages is easy horizontal scalability. As such features can be added to the database with relative ease
    3.The tradeoff with the SQL database is security (for instance for financial institutions, and vertical growth in case of large organisations/databases
  3. While NoSQL has scale advantages, in case relationships are important the recommended DB would be a Relational database such as MySQL
2 Likes
#242
  1. fast, scalable, lower op cost, lots of data
  2. no
  3. no sql is for high scalabilty, high availabiluty
  4. no: receipient might not receive up to date data
1 Like
#243

  1. Can insert data on the fly, unlike in SQL, where table needs to be created, schema defined, set data types, etc. Most applications today store data in JSON format which NoSQL uses too, unlike relational databases (RDBMS). Therefore, potentially greater compatibility. NoSQL offers higher performance.

  2. Not required because… explained in answer 1. above.

  3. Although NoSQL offers higher performance, it offers less functionality, specifically:

  • you can’t have constraints
  • Joins (function) are not supported
    However, the above functions hinders scalability of a database, therefore, trade-offs.
  1. No, because you should opt for better solutions which provide better security, such as ACID properties - atomicity, consistency, isolation, durability… in the context of centralized database.
2 Likes
#244
  1. more scalable, more flexibility because its simpler to model and structure database, high availability
  2. No
  3. NoSQL has higher scalability but less functionality. If you need a database that doesnt require much functionality and foresee rapid scaling, then it is worthy trade off.
  4. No, SQL should be first choice here
1 Like
#245
    • Scalabilty: Adding additional storage/machines is easily possible = horizontal scaling
    • Flexibilty: There is no need to define a data structure upfront. Changing structures are no problem. Unstructured data can be stored easily
    • In the article high availability is another. But honestly, I don’t understand how this is different to a SQL database

  2. No you don’t. See bullet point 2 of answer 1

  3. More scalability but less functionality than a SQL database. I guess, adding new machines makes it easy to scale but also more difficult in the functionality. It is just very hard (maybe impossible) to use relations between data if there is no clear structure upfront and it is distributed among different machines

  4. Absolutely not. NoSQL, no relationships

1 Like
#246

  • What are some of the advantages of NoSQL databases compared to SQL databases?
    It’s easier and quicker to use and it manages better huge amounts of data (especially if they’re constantly increasing).

  • 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?
    here we’re loosing some aspects related to functionality vs a gained scalability and performance.

  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No,in this case the best choice is the standard SQL.

1 Like
#247
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Scalability 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?
    More scalability with the lost 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. No constraints
1 Like
#248

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The main advantages are :
    a- High scalability
    b- High Availability
    c- Easy to create and update data
    d- Is much faster in most type of operations.
    e- Best choice when we are dealing with huge amount of data

  2. Do you have to defined a strict structure for your data in NoSQL?
    We don` t need to defined a strict structure for data in NoSQL

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL handel Structured or Semi-structured data, it is high scalable and has less functional.

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

No, then the best choice is to use MySQL

1 Like
#249
  1. The advantages of NoSQL compared to SQL database are high scalability and availability. High scalabilit, because NoSQL partitions data and placing it on multiple machines in such a way to preserve the ogres of data for Horizontal scaling. High availability because it can auto replicate data when any familiar data repeats itself to the previous consistent state.

2.No structure needs to be defined.

  1. the trade off is worthwhile when a huge amount of data growing continuously and needs to scale the database regularly and the relationships between data are not important.

  2. NO, it would be better to use SQL to store the relationships.

1 Like
#250

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    In NoSQL databases you can update data much quicker than you would in a relational database(SQL) NoSQL databases can also handle large amounts of data better.

  2. Do you have to define a strict structure for your data in NoSQL?
    No. In a NoSQL database, the data usually isn’t strictly defined and changes over time.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Through the use of sharding & horizontal scaling (adding more machines to handle the data), the order of large amounts of data is preserved and protected allowing much room for scalability. However, due to it’s semi structured nature, this system provides less functionality than a relational database.

  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No. In this case a RDBMS (Relational Database Management Systems) would be preferable.
1 Like
#251

  1. Some of the advantages of NoSQL databases compared to SQL databases are; a) you don’t need to create the table before inputting the data, b) they are easier to scale, and c) they are faster in most types of operation.

  2. No. You don’t have to define a strict structure for your data in NoSQL.

  3. Regarding the trade off between scalability and functionality in NoSQL, NoSQL gives less functionality but better scalability.

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

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

they are much faster, easy to scale and you don’t need tables.

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

no you don’t

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

it’s easy to scale but less functionality

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

no then it’s better to use a SQL Database

1 Like
#253
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • NoSQL’s are not structured so it does not matter if the data you are inputting will change over time.
  • They can handle massive amounts of data.
  • Because they are not structured they are faster to use.
  • They use shardng to scale.
  • Data is stored in JSON, which makes it compatible with most applications.
  • High availability

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

  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    Because NoSQL’s are not structured you do not have to plan and strategize your table before you begin work on the database making it easier to scale and faster to use. But because it not structured it have less functionality as regular SQL’s.

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

1 Like
#254

What are some of the advantages of NoSQL databases compared to SQL databases?
• Horizontal Scalability
• Use sharding
• Can deal with huge amounts of data
• Lower operational cost
• JSON format; works with many applications

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?
• Scalibility is great with NoSQL databases because it can use sharding and horizontal scaling to handle more data.
• NoSQL’s functionality lacks when compared to SQL because with an SQL database you can create relationships to link data.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
• No, best to use a SQL database if relationship tracking is the primary focus.

1 Like
#255

  1. more scalability (you can store also huge amounts of data and still have a fast DB), you don’t have problems when your data changes over time

  2. no

  3. while NoSQL is highly scalable we have to handle with:

  • less functionality: on a database level there are no constraints (=no constraints can mean higher risk that your stored data is less accurate)
  • no joins on dabatase level (=e.g. we can not combine fields from two tables by using values common to each table)

However, if the need is for scalable and fast databases that don’t necessarily need to represent relations between data, NoSQL DBs are the best choice.

  1. No, in this case the better choice is a RDBMS.
    However, if I understood it right in the article, some characteristics of RDBMS (constraints, join) can be added at the application level of NoSQL databases, for example if we use a NoSQL DB like MongoDB.
1 Like
#256
  1. High scalability, high efficiency, high availability of data
  2. No
  3. In NoSQL functionality/relationships are not important, scalability is more important because data is quickly added. Therefore NoSQL is better for those cases
  4. No
1 Like
#257
  1. NoSQL databases allow for more rapid scaling and faster processing.
  2. No you dont (its one of NoSQL’s primary benefits vs MySQL)
  3. NoSQL is less functional than mySQL (doesn’t allow for JOIN and constraints) and more scalable than MySQL (able to store and retireve huge amounts of data)
  4. No, if relationships are your focus for a database then you should stick with mySQL.
1 Like
#258
  1. NoSQL databases are faster, require less structure and can be easily scaled up.

2.No.

3.Whilst NoSQL is faster and more scaleable it allows for less functionality.

  1. No. Use SQL.
1 Like
#259

What are some of the advantages of NoSQL databases compared to SQL databases?
The main advantages are high scalability and high availability. (But also fast, easy, and not needed a strict structure)
Do you have to defined a strict structure for your data in NoSQL?
No, you don’t
What can you say about the trade-off between scalability and functionality in NoSQL?
Structures data like SQL gives more functionality but less performance. The trade of, between large amounts of unstructured data that need to be quickly stored and retrieved or structured relationships data
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No a SQL is a better choice then

1 Like
#260
  1. **What are some of the advantages of NoSQL databases compared to SQL databases?**fast and stores large amounts of data
  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 stores large amouns of data quickly, however less user functionality
  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