SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#81

1 What are some of the advantages of NoSQL databases compared to SQL databases?
No SQL is a highly scalable DB which is performance rich. It is also a more efficient DB for storing large amounts of data that does not really change over time and great for creating, deleting and editing data. Unlike SQL there is no join functions needed in the database as it is not sufficient for relational functions. NoSQL also does not require any schema structuring before entering data into the DB unlike SQL.

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?
Well! because NoSQL has very limited functionality the trade-off is ideal. Large amounts of data that rarely changes needs scalability for it’s functional performance as there is little functionality needed other than create, update, delete.

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

#82

Quicker, easier to scale and faster.
No.
Scalability and performance is better versus functionality.
No SQL is more suitable for that.

#83

1 NoSQL databases are scalable, fast and not realational
2 no
3 It has less functions, but is faster.
4 No, because it nor relation database, probable it best to use SQL.

#84
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • 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.
  1. Do you have to defined a strict structure for your data in NoSQL? NO
  • The data is not structured and changing over time
  1. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL has limited functionality at the database level where the following fucntions are not supported and hinders the scalability of a database:
  • You can’t have constraints in NoSQL
  • Joins are not supported in NoSQL
    Exception: Using NoSQL database like MongoDB, you can implements these functionalities at the application level.

RDMS of greater functionality but at the database level vs needing to handoff to upper application level

  • You can define constraints in RDMS
  • Joins are supported in RDMS
  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? It depends.
    Here’s Why:
  • Use RDMS if the relationship between the data you store is too important; NoSQl would not be the best option
#85

What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL is better for scaling huge amounts of data, it has high availability, and it does not require initial definitions before adding 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 has high scalability at the cost of less functionality when compared to relational databse management systems.

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
A relational database will likely be better and more flexible over time than a NoSQL DB.

#86
  1. Some of the advantages of NoSQL databases compared to SQL databases are high scalability and high availability.
  2. You do not have to define a strict structure for your data in NoSQL.
  3. **What can be said about the trade-off between scalability and functionality in NoSQL is that with less functionality, you get greater performance.
  4. If your data has important relationships that you need to keep track of, it is NOT a good idea to use NoSQL.
#87

  1. Some advantages of NoSQL databases compared to SQL databases : they are easy to scale because you can change the structure afterwards ; they are faster ; the are more efficent for streams of datas and for huge amount of data.

  2. You don’t have to defined a strict structure for your data in NoSQL, you can fill the data anyway and the structure can be changed afterwards.

  3. In NoSQL there is a trade-off between scalability and functionality : NoSQL can have no constraints and no joints (less functionalities, but you can implement them at application level) but NoSQL is more rapid.

  4. If your data has important relationships that you need to keep track of, it is not a good idea to use NoSQL because you need SQL relationship capabilities in order to optimize your database.

#88

  1. NoSQL databases are more scalable (because they support horizontal scaling/sharding), faster, replicate their data automatically, and you can more easily make changes.

  2. There is no requirement for a strict structure in NoSQL. You can even change the current data structure. This in particular is a reason why you would want to use NoSQL over SQL.

  3. The higher scalability and ease of changing data comes at the cost of functionality and security. When the different types of data is limited, but the amount of data is very large, or is subject to recurring changes, a NoSQL database is worth the trade-offs. The trade-off in terms of functionality is that you have to implement the functionality, which an SQL database would provide, into the application itself.

  4. When relationships are important, a relational database (SQL) is the way to go.

#89
  1. Scalability (can be horizontally scaled), high availability due to auto replication across many servers.
  2. No
  3. You get the advantage of scalability, simpler structure data but if you do get joins and ability to use constrains. Consistency not guaranteed.
  4. No. SQL is a better solution due to the importance of relationships.
#90
  • No or minimal structure
  • Faster
  • Native JSON support
  • High scalability

  1. No there is no need to define a strict structure

  2. The impact of the trade off depends on the field of application. If your demand is to retrieve large amounts of data as fast as possible and you are constantly adding large amounts of data the trade off do not have a big impact. The impact may be much bigger if the data added have strong relational character in this case you would probably be better off to sacrifice the speed and scalability in favour of functionality.

  3. No, for data with strong or important relations it is recommendable to use RDBMS/SQL.

#91

  1. The advantage of NoSQL over SQL is that data can be added easily, easier to scale and faster operation

  2. NoSQL data can be added on the fly, so you do not need to define a strict structure as with SQL

  3. NoSQL can scale well at the cost of security, scenarios as banking a more relational and data enforcement is required

  4. Relationship required data an NoSQL would not be suitable

#92

  1. Compared to SQL databases, NoSQL databases have a few advantages. NoSQL databases do not need to have a static structure (that is, additional columns can be added in the future), they are much faster in most operations because they are eventually consistent (rather than strictly consistent), and they can scale more easily using the technique of sharding.

  2. You do not have to define a strict structure for data in a NoSQL database.

  3. While NoSQL databases are highly scalable and performant, they lack functionality such as constraints and joins.

  4. It would not be a good idea to use NoSQL.

#93
  1. scalability and speed.
  2. no.
  3. for speedy scalability, it outperforms SQL.
  4. no it isn’t.
#94

NoSQL Database - Reading Assignment
1. What are some of the advantages of NoSQL databases compared to SQL databases?

  • high availability
  • high scaleability
  • using 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?

  • There are less functionality but a better scalability in NoSQL Databases

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

  • No, SQL Database would be a better choice.
#95
  1. NoSQL is very easy to scale, much faster in most database operations, often better for huge amounts of data, and has high availability (due to auto replication to the previous consistent state).
  2. No
  3. When working with large amounts of data, if Joins and Constraints are not requirements, then NoSQL might be the better choice because of its easy scalability.
  4. No, probably an SQL or similar database would be better.
#96
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Less structure required.
    Can handle and store large quantities of data that can be retrieved quickly.
    High scalability and high availability.
    Does not require relationships to be able to function efficiently.
  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 want a structured database that gives you accurate, structured information like in a Banking enviroment, then NoSQL is not recommended. NoSQL has the ability to store large amounts of data, more scalable, high performance and 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
#97
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL databases are more scalable, simpler and offers finer control over 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?
    If large amounts of unstructured data needsto be saved and accessed quickly, and the relationship data are not important, then NoSQL is better.
  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 better to use SQL in this case.
1 Like
#98
  1. Some of the advantages of NoSQL databases compared to SQL databases? is high availability and high scalability.
  2. There is noneed to define a strict structure for your data in NoSQL.
  3. The trade-off between scalability and functionality in that NoSQL is that the database can`t handle constraints and joins at the database level. This functionality must be handled at the application level.
  4. It is not a good idea to use NoSQL database If the data has important relationships that needs to be tracked.
1 Like
#99
  1. NoSqQL databases are easier to scale and much faster for most types of operations, data is stored in JSON format, has auto replication feature
  2. No
  3. You are trading the ability to have joins and contraints functionality in order to have higher performance
  4. No you should use a SQL database in that situation
1 Like
#100

Nosqldb’s are faster to update and create.
Nosql db’s are less or semi structured.
It is better when there is a huge amount of data that does not have relationships.
No, MySql is better.

1 Like