SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#101

Scalable, retrieves huge amounts of data, better performance, allow continuous growth of data, with less need for structured data.
2.
No, using JSON format to retrieve data, there is no need for strict structure of data.
3.
As NoSQL is highly scalable, fast and high performance, enables the management of huge amounts of data, in detriment of less room for functionalities.
4.
No, in this case, would be of better use a Relational Database Management System, SQL would keep a strict structure of the data.

1 Like
#102

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    No need to define the structure of the data beforehand.
    It’s more scalable and faster.
    It’s better to handle large amounts of data.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No we don’t.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL is more scalable compared to SQL but it comes with less functionality (the database is less complex).

  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 case the use of a relational database is better.

1 Like
#103

1.Scalability and flexibility and fast
2.no
3. SQL limits scalability while NoSQL limits functionality
4.no

1 Like
#104

What are some of the advantages of NoSQL databases compared to SQL databases?
High scalability: NoSQL database such as MongoDB uses sharding for horizontal scaling. Sharding is partitioning of data and placing it on multiple machines preserving order of data. Vertical scaling is adding more resources to the existing machine while horizontal scaling means adding more machines to handle the data. Vertical scaling is not that easy to implement, on the other hand horizontal scaling is easy to implement. Horizontal scaling database examples: MongoDB, Cassandra etc. Because of this feature 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 feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state.

You can restructure in NoSQL

Depending on project needs, functionality may need to prevail over scalability. If you only have a few relationships that don’t require constraints and joins, and have a huge amount of data, NoSQL may be the best choice. Otherwise, SQL is probably a better choice.

1 Like
#105
  1. Fast, scalable, limited structural setup, lower operational cost, hold lots of data.
  2. No
  3. High scalability. Little functionality.
  4. No
1 Like
#106
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    {NoSQL}
  • Fast (Data can be updated on the fly)
  • Highly Scalable
  • Highly Available
  • Low cost
  • Non relational
  • Simple
  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?
  • Structured Data provides more functionality. Whereas NoSQL provides higher performance and scalability.
    In NoSQL you don’t have constraints 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, it is better to use SQL as a database. Relationships are best preserved with SQL
2 Likes
#107

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

  • Store and retrieve huge amount of data
  • If data is growing it is easy to scale

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?
In noSQL databases you can’t have constraints, and joins are not supported, making NoSQL more scalable but less functional
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 a SQL database for relational data

1 Like
#108

What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL DBs allow you to have a less structured DB. This allows more scalability and high availability.

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

No. You can modify it on the fly.

What can you say about the trade-off between scalability and functionality in NoSQL?
The scalability of NoSQL comes with a cost of a small amount of functionallity. Constraints and joins aren’t allowed in NoSQL DBs. But if you are handling a large amount of data and growing rapidly NoSQL may be the way to go. the constraints and joins can be handled on the application level.

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No. SQL (RDBMS) are better suited for this type of data.

1 Like
#109
  1. The advantages of NoSQL databases are storing large amounts of data that is unstructured and non-relational.
  2. No strict structure for your data is not required in NoSQL
  3. NoSQL provides more scalability but less functionality
  4. No, NoSQL is not good at managing data relationships
1 Like
#110 
What are some of the advantages of NoSQL databases compared to SQL databases?

Scales easily and can handle huge amounts of data, less complexity/structure needed.

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?

Easier to scale a NoSQL twords huge amounts of data, trade of is functionality that has to be implemented at application level.

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

No, stick to SQL och GraphDB depending on complexity of relationships.

1 Like
#111

  1. SQL - Structured Query Language is a predefined table database - it is not easy to add fields once the database is created, and is a more fixed or ‘hard-wired’ type of setup. It has benefits as well as drawbacks. NoSQL on the other hand is more like a set of tables of tables, and the fields have far more flexibility. This is great for fast, reactive scalability on-the-fly and uses ‘sharding’ for storage. I found this useful - SQL vs NoSQL or MySQL vs MongoDB

  2. Not having to define a strict data structure at the outset in NoSQL makes it much more flexible. In NoSQL the tables can be varied, and elements can be added in easily, and do not have to follow any strict input field requirements or limitations.

  3. While NoSQL is more scalable and flexible, is has less security and is less reliable at a fundamental level in terms of data integrity. SQL has what is called ACID - Atomicity - Consistency - Integrity - Durability. Atomicity means that a TX is either completed 100% or not at all. This would be useful in a power shutdown or other outage, for example, because the TX has either executed fully, or it has not. NoSQL is harder to update definitive values across multiple fields.

  4. No, because data is more decentralised on NoSQL and the fields are not as fixed. It is harder to manage and update this type of data, such as items for sale on a website. These items will not vary or need updating much, and this is better done using SQL.

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

High Scalability and High Availability

  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?

With NoSQL you have less funcionality but a higher performance. On the contrary, SQL DB provides more functionality but gives less performance.

  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 a good idea, better to use SQL DB

1 Like
#113

  1. What are some of the advantages of NoSQL databases compared to SQL databases? Speed of queries, table/field changes/flexibility, high scalability (large amount of data) and high availability are the main advantages of NoSQL databases.

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

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Joins and constraints aren’t supported in a NoSQL database so the trade-off is for more scalability 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, it is better to use a SQL database in this situation.

1 Like
#114

  1. Faster, simpler, can handle huge amounts of data, better scalability, data can be updated

  2. no

  3. NoSQL provides better performance, while having less functions

  4. no

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

  • Speed efficient: the database structure is very simple, making it highly efficient when a query is executed, meaning the query result is very fast to solve.

  • High scalability: NoSQL database such as MongoDB uses sharding for horizontal scaling. Sharding is partitioning of data and placing it on multiple machines in such a way that the order of the data is preserved. Because of this feature 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 feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state.

  • Simple Database Structure No database structure needs to be defined since data will not have anykind of relation with other databases.

  • Faster data traffic: It can perform data traffic (lot of data activity like creating or reading a database) faster, allowing it to deal with huge amounts of data.

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

  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    Depending on the data you need to manage, easy to remember is that NoSQL is highly scalable if the data you have to deal, is not in need of “relationships” between other databases.

  3. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? It will be terrible idea, simple fact that NoSQL databases CAN NOT handle relationships, so is not even close to be an option for “an important data with relationships”

1 Like
#116
  1. Can better process large volumes of data, like when data is recorded every second. NoSQL has a high scalability and high availability.
  2. No.
  3. You cannot join data tables or have relations between data. Also updating/data entry constraints in data tables are not possible. So NoSQL has less functionality as a trade-off for scalability.
  4. No. Use a relational database for that as NoSQL databases don’t support relationships and joins.
1 Like
#117
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • Easier to scale
  • Good for huge amounts of data
  • Much faster in most types of database operations

  1. Do you have to define a strict structure for your data in NoSQL? No, which is advantageous when dealing with large amounts of data.

  2. What can you say about the trade-off between scalability and functionality in NoSQL? Relational DB systems provide consistency and intergrity by enforcing ACID propertires (Atomicity, Consistency, Isolation and Durability) which can be important in some cases, yet can be slow with performance overhead. NoSQL databases such as MangoDB a Cassandra have high scalability and availablity and data is stored in JSON format compatible with most worls applications.

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

1 Like
#118
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High Scalabilty and 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?
    Functionability
  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
#119

Easy to scale, easy to create, insert, delete, update data, high availability

no

scaleabilty and performance are high, but the functionality is low

no, if relations/functionality is important, you shouldn’t go for noSQL

1 Like
#120
  1. One advantage to NoSQL is its good for large storage of simple repetitive data streams.
  2. NoSQL doesn’t have any real structure because its not in columns nor is it relational.
  3. The NoSQL trade off between scalability and functionality are first its less secure and prone to data update latency, in exchange for its scalability and speed.
  4. you shouldn’t use NoSQL for data that is dependent upon its relationship to other data.
1 Like