SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#201

1.What are some of the advantages of NoSQL databases compared to SQL databases?
They are much faster in most types of operations that we perform on database.
They are high scalability and high 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?
SQL gives more functionality but less performance.

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

1 Like
#202

What are some of the advantages of NoSQL databases compared to SQL databases?
High availablity
High Scalability

Do you have to defined a strict structure for your data in NoSQL?
Yes. and it has to be in place before the data arrives

What can you say about the trade-off between scalability and functionality in NoSQL?
There are disadvatnages in using NoSQL but these can be offset at application level

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL
It’s not ideal. RDBMS is better for establishing relationships between data

1 Like
#203
  1. the Advantage of a noSQL DB is that it provides alot of storage and availability on demand.
  2. No you do not have to define a strict structure for the Nosql format.
  3. The rade-off all depends on the person and what they are need a database for. Nosql provides alot of scalability but doesnt have the functionality to operate like sql. to connect data in large groups together. So understand the pros and cons and what the project requires is key before implementation.
  4. No it is not a good idea to use NoSQL if you need to continuously track relations
1 Like
#204

Glenn_CostaRica

1. What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL databases offer high degree of scalability and flexibility. These have the capacity to partition data and store it in multiple devices through sharding. A NoSQL option, then, can manage big amounts of information easily and the database itself can expand as the amount and variety of data grows.

2. Do you have to define a strict structure for your data in NoSQL?
No. It is not necessary to structure rigidly the data in NoSQL and you can change the types of data stored in the system in a dynamic way as the data accumulates.

3. What can you say about the trade-off between scalability and functionality in NoSQL?
The trade-off between scalability and functionality does not occur in such a pronounced degree as in SQL databases. NoSQL databases can usually scale while keeping and improving functionality.

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
If you need to keep track of a lof of critical relationships, it is not a good idea to rush to choose a NoSQL option without studying very well your case. In general, SQL databases are hard to beat in the terrain of storing data on relationships.

1 Like
#205
  1. They are more easily scaled and work faster with huge amounts of data and have less overhead.

2.no.

3.NoSql doesn’t support constraints or joins to be more scalable.

4.no NoSql does not have a way to create relationships between datasets at a database level.

1 Like
#206
  1. a)To Store and Retrieve large amounts of Data
    b) Data relationships are not as critical as required in SQL RDBMs
    c) Constraints and Joint’s not required as they impact of the performance of the DB
    d) When there is a need to frequently up scale the size of the DB
    e) Data does not need to be structured and it changes over time
  1. No
  2. Scalability : Due to the fact that NoSQL’s use Horizontal Sharding they are able to scale much better than SQL RDBs however NoSQLs do not have the same amount of functionality at the DB level e.g. lack of support for Joins which must be implemented at the application layer
  3. It may be better to use an SQL based RDB
1 Like
#207
  1. NoSQL databases are more scalable and can be changed after they are already in use.
  2. No, a strict structure does not have to be defined in NoSQL DBs, they can be amended and adapted as needed while the data streams are coming in.
  3. It just depends on what type of DB someone needs. If the data is relatively simple and non relational but there is a high/continuous quantity, a NoSQL DB would be better. But if the data is relation-heavy and there is less of it SQL would be the better choice.
  4. No, SQL would be better suited.
1 Like
#208
  1. Performance and scalability
  2. No
  3. Scalability-You can update and add huge amount of data and have no constraints and therefore gives you more performance. With functionality you have more structure (columns and rows),thing are more departmentalized and offers integrity and consistency, but lacks speed and scalability.
  4. No
1 Like
#209

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

Carlos Z.

2 Likes
#210
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

Some advantages of NoSQL databases are high scalability, and high availability. Highly scaleable because both horizontal and vertical scaling are possible, and highly available because of auto replication.

  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?

If you need to store huge amounts of data, that may be regularly changing, and tracking the relationships between that data is not critical, a NoSQL database can be useful. It’s easier to scale and restructure data in a NoSQL database than in an SQL database, though a NoSQL database has more limited functionality in terms of tracking relationships.

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

No, it’s better to use an SQL database.

1 Like
#211
  1. It’s much more scalable and faster, You can change and redefine data on the go with no trouble.
  2. Nope you can do it on the go
  3. It’s a matter of choice of what’s important for the service. If you need Functionality and data relationship is important then you’ll have to sacrifice the scalability and vise versa.
  4. No, Better to use SQL
1 Like
#212
  1. NoSQL databases are more efficient in dealing with huge amounts of data. They have high efficiency and high availability since they can implement sharding which is horizontal scaling (on different machines instead of overloading one).
  2. No
  3. NoSQL has high scalability but SQL has high functionality. NoSQL don’t have constraints and joins that SQL has and gives it more functionality.
  4. No
1 Like
#213

scalability

no

depends on the circumstances, the ‘critical nature’ of the data. one must weigh the risk of eventual consistency being a serious issue

no, may not be current

1 Like
#214

NoSQL Databases - Reading Assignment

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

Limitations of Relational Databases - SQL

• In relational database we need to define structure and schema of data first and then only we can process the data.

• Relational database systems provide consistency and integrity of data by enforcing ACID properties (Atomicity, Consistency, Isolation and Durability). However in most of the other cases these properties are significant performance overhead and can make your database response very slow.

• Most of the applications store their data in JSON format, RDBMS don’t provide you a better way of performing operations such as create, insert, update, delete etc on this data.

Advantages of NoSQL

High scalability:

• Sharding is partitioning of data and placing it on multiple machines in such a way that the order of the data is preserved.

• Vertical scaling means adding more resources to the existing machine; Vertical scaling is not that easy to implement.

• Horizontal scaling means adding more machines to handle the data, on the other hand horizontal scaling is easy to implement. Horizontal scaling database examples: MongoDB, Cassandra etc.

• NoSQL can handle huge amount of data, as the data grows NoSQL scale itself to handle that data in efficient manner.

High Availability:

• Auto replication features in NoSQL makes it highly available because in case of any failure data replicates itself to the previous consistent state.

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

• There is no need to define a strict structure for your data since it can insert, update data on the fly.

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

• In NoSQL the advantages are High Scalability and High Availability.

*Structured or semi structured data, less functionality and high performance

• NoSQL has Constraints and Joins support is not required at database level.

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 relational database like SQL; it is a structured data that provides more functionality but gives less performance.

1 Like
#215

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

Carlos Z.

#216
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The main advantages are high scalability and high availability. Auto replication feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state. Other advantages:
  • Faster.
  • Horizontal scaling
  • Can handle large quantities dynamic of data.
  • Data can be inserted and updated on the fly.
  • Simpler.

  1. Do you have to defined a strict structure for your data in NoSQL?
    No need.It’s easy to change it later on.

  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    In NoSQ there are less functionality. For example,
    You can’t have constraints in NoSQL
    Joins are not supported in NoSQL
    You use 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.

  3. 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.

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

It is easier to scale and provide high performance at a lower cost and you do not need to define the database structure. The NoSQL database is well suited for large volumes of data.

  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?

There is less functionality but that is the tradeoff you need to make in order to achieve better scalability. The NoSQL database is therefore less suited for relational databases.

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

What are some of the advantages of NoSQL databases compared to SQL databases? They have high scalability a better performance, they´re faster.
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? No SQL databases are have higher scalability so they´re more suitable where there are huge amounts of growing data that but the relationship between data is not that important, so functionality isn´t as necessary.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No

1 Like
#219

  1. you can store large amounts of data plus it’s easily scalable

  2. No

  3. SQL provides more functionality than performance

  4. No

1 Like
#220

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High scalability by using sharing as a horizontal scaling and high availability with the auto replication feature.

  2. Do you have to defined a strict structure for your data in NoSQL?
    Required for SQL dBs, not for NoSQL dBs.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    In order to bring efficiency on fast operations working with a high amount of data, scaling is more important therefore NoSQL dBs, could meet these needs. In this case, functionalities are better implemented on the application layer, rather than on dB.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    Relational Database Management Systems like SQL makes more sense in this case.

1 Like