SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#161

What are some of the advantages of NoSQL databases compared to SQL databases?
Less cost, more scalability of data, no strict structure of data.
Do you have to defined a strict structure for your data in NoSQL?
No unlike SQL
What can you say about the trade-off between scalability and functionality in NoSQL?
The trade off would be that it is more scalable in terms of the ability to store much more data, therefore more flexibility with ease of management also the ability of data to be stored easier.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No for data relationships NoSQL would be unsuitable. SQL would be better.

1 Like
#162
  1. High scalability and availability.
  2. You have structured or semi structured data.
  3. When you don’t want to store and retrieve huge amount of data and the relationship between the data you store is very important and the data are structured and changing over time and the data is not growing continuously.
  4. No
1 Like
#163
  1. Scalability and fault tolerance
  2. No. NoSQL is made for storing massive amounts of data with minimal structure
  3. It’s not so much of a trade-off. If you need relations, SQL is the clear choice. For all other flat database needs, a NoSQL like MongoDB.
  4. In a word, no
1 Like
#164
  1. High scalability and availability. Optimized towards handling large amounts of information.
  2. No.
  3. It is trade of that must be taken into consideration depending on what kind of application is going to be built. Do I depend on high integrity of my information or do I need high performance?
  4. It would be better to use a relational database for this use case. As there will be higher integrity and fidelity of the information.
1 Like
#165
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    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. Do you have to defined a strict structure for your data in NoSQL?
    No, using JSON format to retrieve data, there is no need for strict structure of data.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Structured Data provides more functionality. Whereas NoSQL provides higher performance and scalability. In NoSQL you don’t have constraints and joins are not supported
  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 a SQL database in this situation.
1 Like
#166
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    No schema predefinitions needed,
  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?
    Easy to scale means huge amounts of data and this is the tradeoff for structured data in SQL, therefore it is not that easy to scale but guarantees more functionality
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    Probably not because joins are not possible e.g.
1 Like
#167
  1. Easy to scale, faster, can handle huge amounts of data, data is in JSON format (=more compatible with applications)
  2. No
  3. When theres alot of data coming in all the time and there is need for flexibility, scalability is preferred over functionality
  4. No
1 Like
#168
  1. High scalability and availability.
  2. No.
  3. To achieve high scalability, one must sacrifice functionalities like CONSTRAINTS and JOINS (At least at database level, they can be implemented at the application level).
  4. No.
1 Like
#169

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    They are highly scalable and available (fast and error proof)

  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 cannot use Join queries and have constraints.

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

1 Like
#170

  1. NoSQL databases are more scalable and faster in most type of operations than SQL databases are.

  2. No, you don’t have to. You can insert and update data as you go.

  3. NoSQL has less functionality and more scalability. You don’t have constraints in noSQL and joins are not supported.

  4. No, better use SQL then.

1 Like
#171

High scalability, no need to setup a strict structure of the db, speed in managing huge quantity of records.

2
No, this step is more simple.

3
NoSQL uses horizontal scaling that’s more simple to implement: It’s sufficent to perform the sharding of the data onto more and more servers while the db grows.

4
No, RDBMS are more suitable if the company has a db where the relationship among many columns is important.

1 Like
#172
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Faster, can handle large amounts of data better, you can have different number of fields/input per entry, no need for defining strict structure
  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?
    Functionality is on the lower end of things, but scaling is really good and easy
  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
#173

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL databases are easier to scale and better at handling very large amounts of data,

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, they rather stored the data as a continuous stream of JSON data.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Wjile NoSQL databases are quick and scalable because of their reduced complexity they do not allow for complex relations between data stored in the database. This can reduce the functionality of the databse itself and means that this functionality would have to be built into a different part of the app design.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    This would be an instance when an SQL database would be preferable to a NoSQL framework.

1 Like
#174
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Speed, scalability, high performance
  2. Do you have to defined a strict structure for your data in NoSQL?
    No, that is not necessary
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    having a huge amount of data with no relations
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, you can implement relations in application layer
1 Like
#175
  1. NoSQL databases are more scalable, highly available and faster than SQL databases for most operations.
  2. No strict structure has to be defined for NoSQL.
  3. Structured or semi structured data, less functionality and high performance and scalability.
  4. No, relationships is the strength of an SQL database which should be chosen in this case.
1 Like
#176

1- faster, non relational, easily scalable, and simpler
2- No
3- SQL gives more functionality, but less performance.
4- No, only use SQL for important documents.

1 Like
#177
  1. low cost, easy to scale, doesn’t need detailed structure
  2. no
  3. Worth it if you’re dealing with large streams of data when data reliability isn’t as important.
  4. no
1 Like
#178
  1. NoSQL databases are highly scalable and have better availability
  2. no, that’s the point of having a NoSQL database, it is not necessary to define the relationships and structure of data since you can replace and delete data.
  3. You have to think of what is more important for your needs, adding new data fast and change data easily, than NoSQL makes sense. But over time if your needs are changing and the relationship between data becomes more important you should consider functionality as a more important need.
  4. No, you should use a rational database and not NoSQL.
1 Like
#179
  1. thy are easier to scale and much faster.
  2. no.
  3. the trade offs is worth it if you need speed and scalability.
  4. no better to use sql.
1 Like
#180
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • Scalability and high avalaibility. Handles huge amounts of data,. Easy to scale and update. Fast.
  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?
  • To store and retrive large amounts of data fast, the trade-off is worth it.
    You can’t have constraints in NoSQL and Joins are not supported.
  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