SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#542

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

    It is easy to scale and offers mor performance.

  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 offer more scalability but reduced functionality.

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

1 Like
#543

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

    NoSQL

  • Handle large volumes of data at high speed with a scale-out architecture.
  • Store unstructured, semi-structured, or structured data.
  • Enable easy updates to schemas and fields.
  • Be developer-friendly.
  • Take full advantage of the cloud to deliver zero downtime .
    SQL
  • Speed
  • Well defined standard exits
  • No coding required
  • Security - Atomicity
  1. Do you have to define a strict structure for your data in NoSQL?

NO

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

When data is continuously changing over time and the need of updating the data is frequent, having the freedom of scaling is available, but sacrificing its functionality.

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

Absolutely not.

1 Like
#544

What are some of the advantages of NoSQL databases compared to SQL databases?
In SQL you to be sure about the structure of tables, fields, schema, data types of fields etc before inputting data, NoSQl on the other hand gives Devs the freedom to insert, update data at any time.
Do you have to define a strict structure for your data in NoSQL?
NO, because the freedom NoSQL gives allows for DEVs to be flexible with the database not making things static. This presents the opportunity to let the project or product to Vertical scale and horizontal scaling to if user needs and demand.
What can you say about the trade-off between scalability and functionality in NoSQL?

  1. You can’t have constraints in NoSQL
  2. Joins are not supported in NoSQL
    These supports actually hinders the scalability of a database, so while using NoSQL database like MongoDB, you can implement these functionalities at the application level.
    If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    NoSQL databases will be slow if they deal with relational data so the answer is NO.
1 Like
#545

image
image831×742 131 KB

2 Likes
#546
  1. NoSQL advantages over SQL databases, include the ability to handle huge data volumes, deal with changing data structures, with high levels of scalability and availability due to Sharding and Auto-Replication
  2. You have to defined a structure for your data in NoSQL, but NoSQL is designed to be able to evolve that structure ‘on the fly’
  3. Use SQL if the application needs to make use of Joins. (There’s also a strong case for using SQL if that’s all your team is familiar with.) Otherwise NoSQL is much easier to setup and evolve
  4. If your data has important relationships that you need to keep track of, it wouldn’t be a good idea to use NoSQL. It’s possible to do the equivalent of a ‘join’ with NoSQL but it’s difficult to do, and it’s not what NoSQL was designed for
1 Like
#547

1.) Horizontal scaling helps keep data in an orderly fashion and is easy to implement. In any case of failure data replicates itself to the previous consistent state.

2.) There is no need to create tables, define schema, or set data types.

3.) Because there is more scalability and performance, NoSQL cannot have constraints or joins.

4.) You would rather have a relational database.

1 Like
#548
  1. The main advantages are high scalability and high availability.
  2. No
  3. NoSQL has better scalability and performance, but SQL has better functionality. It’s a trade off.
  4. No
1 Like
#549
  1. NoSQL can handle huge amount of data, uses ‘sharding’ - partitioning of data allocating it to number of machines to handle and preserve. As it can handle huge amounts of data it scales itself to handle the data in efficient manner. It’s non relational, does not require the structure of data required by SQL, cost
  2. No
  3. when you need performance, the option of handling of huge amounts of data and scalability is important you can trade off the option for structured, relational data handled by SQL
  4. No as SQL will be the preferred choice for handling structured relational data
1 Like
#550
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  2. Do you have to defined a strict structure for your data in NoSQL?
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?

1 - NoSQL in better for storing huge amount of data , he data is growing continuously and you need to scale the database regular to handle the data etc.
2 - No , you can insert, update data on the fly.
3 - NoSQL is less structured there for it is more scalable but less functional.
4 - No

1 Like
#551

1/Highly scalable, because data are sharded
2/ No need to define a structure prior entering data
3/ SQL allows constraints and joins// noSQL don’t, then functionalities are less developed than SQL DB, but simple queries (i.e. retrieve, update…) are more speeded, especially when is huge
4/ No, relationships functions are efficient in SQL

1 Like
#552

  1. low cost, high scalability, non relational, speed, handling large quantities of data.

  2. No need to define structure.

  3. NoSQL has better scalability than functionality.

  4. No.

1 Like
#553
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • scalable
    Low cost
    You don’t need the structure before beginning
  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?
    **
  • the scalability is in a reverse relation to the functionality
  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
#554
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Can better handle huge amount of data and the replication feature makes them more available.
  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 cannot handle JOINS and CONSTRAINST, although these functionalities can be added at the application layer. If you want to manage huge amount of data and you are not so concern about the type of DATA and the relationship among them, then NOSQL
  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
#555

SQL and Relational Databases - Reading Assignment:

Q1:What are some of the advantages of NoSQL databases compared to SQL databases?
A: Compared to SQL databases some of the advantages of NoSQL databases are:
NoSQL databases are much easier to scale and they are much faster in most types of operations that we perform on a database. When dealing with huge amounts of data the NoSQL database is the best choice. With relational SQL databases it’s necessary to define the structure and schema of data first and only then can data be processed. SQL database systems provide consistency and integrity of data by enforcing ACID properties (Atomicity, Consistency, Isolation, and Durability).

Q2: Do you have to define a strict structure for your data in NoSQL?
A: There is no need to define a strict structure for data in a NoSQL database.

Q3: What can you say about the trade-off between scalability and functionality in NoSQL?
A: The trade-off between scalability and functionality in NoSQL results in structured or semi-structured data, less functionality, and high performance.

Q4: If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
A: If your data has important relationships that are necessary to keep track of, it’s not a good idea to use a NoSQL database for such a task.

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

Highly scalable due to horizontal sharding, which means partitioning data across multiple machines while maintaining the order of the data.

Data will replicate itself to the previous consistent state in case of failure.

This makes it better for storing huge, constantly expanding datasets where the relationship between the data doesn’t really matter.

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

You do not have to define a strict, immutable structure for data in NoSQL.

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

One leads to the other - reducing functionality around atomicity, consistency, isolation and durability cuts down on the processing power needed to operate the database. This enables the processing power to be focused on different needs, better enabling the storage and retrieval of large datasets that would be impractical in 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?

Potentially, if the dataset is particularly large it could be useful to use NoSQL as relations between data can be programmed above the database at the application level. However, typically a relational database created to inherently store relationships between data like SQL would be more suitable.

1 Like
#557
  1. Handle large volumes of data at high speed with a scale-out architecture. Store unstructured, semi-structured, or structured data. Enable easy updates to schemas and fields.

2.No

  1. When dealing with lots of amount of data and needing it in real time information.

4.No

1 Like
#558

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

NoSQL

  • Low cost
  • Non-relational
  • Easily scalable
  • No need for detailed database schema

SQL

  • Speed
  • Strongly defined international standards
  • Secure transactions
  • No coding needed
  • Strong analytical, querying ability

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

No, it is not necessary to define a strict structure in NoSQL

3/ What can you say about the trade-off between scalability and functionality in NoSQL?
The trade-off in NoSQL is less functionality in exchange for no constraints or joins, so there is more scalability.

4/ If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Absolutely not, it is more efficient to use a SQL database.

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

Higher scalability and performance.

  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?

In NoSQL databases you have more scalability but less functionality. This is useful when you store a big amount of data and that you don’t have important relationships between 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. In that case it is better to use relational databases.

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

High availability and high scalability.

  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 more scalability yet 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 it is not.

1 Like
#561
  1. Can work with huge amounts of data. Good if the relational aspect of the data is not that important.
    NoSQL is non relational, low cost and easy scalable
    SQL is fast, very secure and needs no coding
  2. No
  3. It*s not as secure but great with high scalability. In case of failure the data replicates itself to the previous consistent state.
  4. It’s not good for relational focused databases.
1 Like