SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#401
  1. Easier for CMS application like a news org, given they publish public documents that can have different properties and those are dynamic
  2. Not necessarily, but it’s highly recommended
  3. It’s important to identify those trade offs and apply and use a NoSQL in the right domain
  4. No, a NoSQL Db can deal with that, but It’s an extra effort to keep the consistency, if your db is all about relationships between multiple collections, then It’s a good sign that you need an RDB
1 Like
#402
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    on NoSQL you can insert/ add data on the fly.
    One of the advantage of NoSQL database is that they are really easy to scale and they are much faster in most types of operations that we perform on database. There are certain situations where you would prefer relational database over NoSQL, however when you are dealing with huge amount of data then NoSQL database is your best choice.
  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?
    The trade off is worthwhile where large amounts of unstructured data need to be quickly stored and retrieved and where relationships between data are not important
  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
#403

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Easy to scale, high availability, large amount of data

  2. Do you have to define a strict structure for your data in NoSQL?
    No or at least less structured than SQL

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL can handle a big volume of data in a performant way bat has less functionality as a SQL DB.

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

1 Like
#404

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Easy to scale, high availability and faster.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No you do not need to create tables, define schema and set data types beforehand such as with RDBMS. In NoSQL you can insert/update data on the fly.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL has better scalability - it can scale horizontally and is good for huge amounts of data which grows over time. But there is less functionality such as can’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?
    It is best to use RDBMS instead.

1 Like
#405
  • High scalability and high availability are the two main advantages of a NoSQL over a SQL database.
  • No
  • NoSQL is easier to scale and input of the data at first goes faster, but on the other hand, on NoSQL you have less queries you can do (finding relationships), because the input does not contain specified tables, hence, less connections to make.
  • No it’s better to use a SQL as described in answer above.
1 Like
#406
  1. You can insert data on the fly, easy to scale, much faster in most types of operations that are performed in databases and high availability.
  2. No
  3. NoSQL scales easyn and is highly performant, but constraints and joins are not supported.
  4. No, if there are important relationships, SQL is preferred due to its strength in representing relations.
1 Like
#407
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

-don’t have to be redefined in advance

-easy to scale

-easy to change

-faster than other databases

  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?

NoSQL is more scalable and fast, but has less functionality (can’t have constraints and no joins available).

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

No, SQL database is designed for this purpose.

1 Like
#408
  1. High scalability and high availability
  2. No
  3. You can implement the nosql shortcomings at application level.
  4. No
1 Like
#409

A. n SQL database you need to define structure and schema of data first and then only we can process the data. Iff you want to change the structure later it will be much less convenient then when you do it with NoSQL
B. NoSQL has High scalability

  1. No

SQL is more focused on functionality and NoSQL is more focused on scalability and performance

No. It is better to use SQL then because these databases are build for that

1 Like
#410

1.)
Storing and retrieving large amounts of data with improved performance.
Easily scaled horizontally for large amounts of data.

2.)
No. All data is stored in json

NoSql databases doesn’t have constraints and doesn’t support joins so they are more scalable with increased performance and but less functional.

4.)
No, in that case is better to use a RDBMS than a NoSQL database.

1 Like
#411
  1. You don’t have to create the tables or set the data types. You can just add data and update it on the fly. Scalability is also an advantage.
  2. No
  3. You can store more data more easily and quickly.
  4. No
1 Like
#412

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    No structured information needed in an NoSQL and it is more scalable.

  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?
    Data can be stored more quick and easily but it is less secure.

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

2 Likes
#413

  1. inserting and updating data on the fly easy scaling and faster in most types of operations we perform in databases

  2. No

  3. NoSQL is better at handling large amounts of data in an easy to scale way. structured databases have much more functionality but are less scalable.

  4. No, it is better to use a structured database

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

NoSQL is better for dealing with huge amounts of data, it can be updated and restructured at any time easily, it has high scalability and high availability.

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

No, this is not necessary in NoSQL like it is in SQL.

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

NoSQL is highly scalable, with techniques like sharding. This means you can handle larger amounts of unstructured data more efficiently. The fact that it is unstructured gives it less functionality than an SQL database because you have no constraints and joins in NoSQL meaning you can not make relationships from the data.

  1. 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 good to use NoSQL for relationship data because it simply does not have the functionality to derive relationships from the data.

1 Like
#415
  1. High availablity and scalability. 2. No need 3. With NoSQL you can implement functionality like join and constraints in the application process, while having scalability and availability. 4. No,it is not.
1 Like
#416

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    -Scalability and performance

  2. Do you have to defined a strict structure for your data in NoSQL?
    No you dont need to, it is way more flexible than SQL

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL its better if you want to store huge amount of data , since it doesnt need to keep relationships between different data entities and keep so many different attributes which makes structure way more complex. On SQL you rely on structure and security , which is better for some use cases as storing critical data for entities that have more information to store while its security is critical.

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

No , in that situation is better using SQL that is structured in a way that you record relations between different entities.

1 Like
#417
  1. SQL DB are relational and can not be easy restructured, NoSQL are non-relational and have a higher scalability and higher availability,
  2. no
  3. structured data is better in functionality but not so good in performance. If you have data which does not need to be structured but has a hugh amount of it go for NoSQL. With some NoSQL DB you can implement the missing functionality on application level.
  4. No
2 Likes
#419

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    One of the advantages of NoSQL is they are really easy to scale and they are much faster in most types of operations that we perform on the database.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, you do not need to define strict structure for your data in NoSQL.

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

    a. You can’t have constraints in NoSQL
b. Joins are not supported in NoSQL4.

    4.If your data has important relationships that you need to keep track of, is it a good idea to use
    NoSQL?    . NO, it would be ideal to consider using a relational database system. It provides
    consistency and integrity of data by enforcing [ACID properties]
    https://beginnersbook.com/2015/04/acid-properties-in-dbms/) (Atomicity, Consistency, Isolation and
    Durability ). There are some scenarios where this is useful like banking system. However in most of
    the other cases these properties are significant performance overhead and can make your database
    response very slow.

2 Likes
#420

  1. Must faster & easier to scale with less requirement regarding structure and can handle larger volumes of data efficiently.

  2. No. This is not a requirement.

  3. Structured data with less functionality but carries a much higher performance and scaleability.

  4. No. Your choice would be SQL.

2 Likes
#421

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

They store the data using sharding (distribution) and are highly scalable in terms of the ease of addition of new machines to such a “horizontal” network. They also offer high availability meaning in any case of failure the data can be retrieved or replicated.

Most common database operations performed in their environment are much faster than in SQL databases.

When dealing with huge quantities of data, NoSQL databases are typically the best choice.

2- Do you have to defined a strict structure for your data in NoSQL?

No. It can be constructed and updated over time.

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

NoSQL databases typically offer high performance with a reduced functionality compared to SQL / relational databases. Conversely, highly-structured SQL / relational databases can be said to offer more functionality but reduced performance.

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

No.

2 Likes