SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#301
  1. 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
  2. No, in NoSQL you don’t have to worry about that, you can insert, update data on the fly.
  3. It’s more scalable and faster than relational databases, and it’s the best choice when you have massive amounts of data. However,you trade functionality for scalability in this case.
  4. No, we should use a relational database in this case.
1 Like
#302
  1. Some of the advantages of NoSQL databases are that they are easier to scale and they can perform faster operations.
  2. You don’t have to define a strict structure in NoSQL. You can add data as you go.
  3. There is a tradeoff between ease of use and scalability - as NoSQL allows you to manage large, increasing amounts of data - with integrity of data - as relational database systems enforce ACID properties.
  4. It would be better to use an SQL if your data has important relationships that you need to keep track of.
1 Like
#303

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL is faster because it doesn’t support some of the structured features of SQL. It also scales better and can handle much larger amounts of data.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, it’s more dynamic in the sense that it can expand as needed.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    I guess it really depends on what you’re looking for, and what type of data you’re planning to store. I would imagine a site like FB would probably need somewhat more of a RDBMS setup than a NoSQL setup, but I could be wrong! The amount of data they store may require, in part at the very least, something more scalable for large amounts of data.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    You would probably want to go with a standard SQL database because it would be more secure.

1 Like
#304

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

    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.

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

    In NoSQL you don’t have to worry about structure, you can insert, update data on the fly.

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

    There are certain situations where you would prefer relational database over NoSQL, when you are dealing with huge amount of data then NoSQL database is your best choice.

  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 not a good idea.

1 Like
#305

Hight scalability and hight availability and import data and update on the go

NO

NoSQL is more scalable and less functional

No, SQL is the relational data base

1 Like
#306

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

It is really easy to scale and NoSQL are most faster in most of types of operations. Dealing with a huge bag with data (develop AI) NoSQL is your best choice for this operations. SQL database is great for these security atomic transactions, it is well defined as a global standard (most of databases use SQL in some way.)

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

No, you can insert and update data on the fly! SQL stands for (Structured Query Language) and now we speak about NoSQL!

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

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

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

No! Using NoSQL when you need to handle huge amount of data, the relationship between the data you store is not that important. Use SQL for important relationships!

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

High scalability; usage of sharding for horizontal scaling (adding more machines to handle the data. Instead of vertical (adding more resources to one machine). Examples MongoDB, Cassandra etc.

High availability; Auto replication (In case of failure any data replicates itself to the previous consistent state)

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

You can, but you don’t have to. It can work as structure or semi structured data, which gives you less functionality and high performance.

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

If you need to handle a huge amount of data with no correlation, best option is NoSQL, you can scale very easily, while keeping an ok functionality. But if you need to associate the data in certain order you need more functionality.

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

No, in this case you are better off with something that would give you more functionality, like SQL.

1 Like
#308
  1. Fast and easy to scale, t, hold lots of data, much faster
  2. No
  3. The trade is very useful when a lot of data needs to be store fast and also retrieve fast in this case the relationship data base is not the perfect one to use
  4. No, better to use a Relationship data base management system
1 Like
#309

1- a- You can insert and update data on the fly.
b- They’re easy to scale and much faster in most database operations we perform.
c- They’re better when dealing with huge amounts of data.
d- They store their data in JSON format, which is compatible with most of the apps
in the world today.

2- No, you don’t.
3- NoSQL has high scalability and performance, but less functionality.
4- No! SQL is the best for connecting important relationships through a series of tables.

2 Likes
#310

article: https://beginnersbook.com/2017/09/introduction-to-nosql/

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    – With NoSQLyou don’t have to create the table, define schema, set the data types of fields etc before you can actually insert the data
    – NoSQL is ideal for dealing with huge amounts of data.

  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 database such as MongoDB provides High Availability through auto replication feature which allows the data to replicate itself to the previous consistent state in the event of a failure
    – NoSQL databases are faster than RDBMS systems when dealing with large volumes of data and they are also easy to scale through sharding for horizontal scaling - which is adding machines and partitioning of data and placing it on multiple machines while preserving the order of the data. Vertical scaling is not as easy but it allows more resources to be added to existing machines.
    RDBMS provides structured data and more functionality but less in performance than NoSQL databases. Whereas NoSQL is structured or semi-structured data with less functionality but with higher performance

  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
#311
  1. High scalability and high availability
    2.no
  2. if you’re dealing with large amounts of data and joins and constraints of of no importance or less importance. No SQL works well.
  3. not a good idea. Better to stick to SQL when joins and relationships are important.
1 Like
#312
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

a) better scalable - easier to add machines and up-grade machines (for big data)
b) higher availability - due to an auto replication functionality

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

no (thats the big advantage. i don´t have to pre-define the whole structure with which it is more flexible if data structure changes.

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

a) you cant have constraints
b) Joins are not supported (no relationships) - since those joins make a database
less scalable

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

no, no relationships possible with NoSQL (since no joins possible)

1 Like
#313
  1. High scalability and high availability
  2. No
  3. When you have a huge database and is constantly changing you would choose NoSQL database and with that trade off the functionality fo a SQL database.
  4. No
1 Like
#314

  1. The advantages are high scalability and high availability.

  2. No

  3. You can’t have constraints or joins in NoSQL, but they are more scalable and you can implement the missing pieces at the application level.

  4. No. SQL will be better for important relational data.

1 Like
#315
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The advantages to a NoSQL database is that it has superior performance and scalability compared to a SQL database.
  2. Do you have to define a strict structure for your data in NoSQL?
    No, unlike a RDBMS, you don’t need to define a strict structure for your data.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    A NoSQL DB allows for superior scaling capabilities vs. an RDBMS but it does not support data integrity via contraints or the ability to join data sets.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, in this case it would be better to use and RDBMS vs. a NoSQL DB.
1 Like
#316

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The main advantages are high scalability and high availability

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, just Structured or semi structured data.

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

  4. You can’t have constraints in NoSQL

  5. Joins are not supported in NoSQL
    These supports actually hinders the scalability of a database, so while using NoSQL database like MongoDB, you can implements these functionalities at the application level.

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

1 Like
#317

Centralized IT Infrastructure

NoSQL Introduction

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

a. Handle Large Volumes of Data at High Speed with a Scale-Out Architecture

b. Store Unstructured, Semi-Structured, or Structured Data

c. Developer-Friendly

d. Take Full Advantage of the Cloud to Deliver Zero Downtime

e. Enable Easy Updates to Schema and Fields

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

No, NoSQL databases allow the data to be stored in ways so that fewer transformations are required when the data is stored or retrieved for use. Many different types of data,(unstructured, semi-structured, structured), can be stored and retrieved more easily, making it easier to adapt to new forms of data.

This is in contrast to Relational databases, which store data in a predefined schema (blueprint of the DB structure ex. tables/col/rows). To use relational databases, a data model must be designed and then the data is transformed and loaded into the database. Then when the data is written back, it must be transformed again back into the relational tables

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

Increased scalibility in NoSQL:

NoSQL databases were created in Internet and cloud computing eras that made it possible to achieve scalability - by spreading the storage of data and the work to process the data over a large cluster of computers. To increase capacity, more computers are easily added to the cluster (Horizontal Scaling).

SQL databases are most often implemented in a scale-up architecture, which is based on using ever larger computers with more CPUs and more memory to improve performance (Vertical scaling). Achieving the same type of scalability with SQL databases can be expensive, require lots of engineering, or may not be feasible.

An example of this speed benefit can be seen with a financial services company like IHS Markit requires high performance both for ingesting data and for delivering it. Moving from a relational database to MongoDB, IHS Markit reports that it is able to deliver timely financial information to its customers 250x faster.

Less functionality in NoSQL:

a) You can’t have constraints in NoSQL - SQL constraints are used to specify rules for the data in a table. they are used to limit the type of data that can go into a table. This ensures the accuracy and reliability of the data in the table. If there is any violation between the constraint and the data action, the action is aborted.
b) Joins are not supported in NoSQL
These supports actually hinders the scalability of a database, so while using NoSQL database like MongoDB, you can implements these functionalities at the application level . `

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

Important relationships would probably be better served with a SQL DB, where it natively embraces relationships - able to store, process, and query connections efficiently. These databases compute relationships at query time through expensive JOIN operations, a graph database stores connections alongside the data in the model.

On the other hand you can use a graph database (a type of NoSQL DB) which is an efficient, constant-time operation and allows you to quickly traverse millions of connections per second per core. Independent of the total size of your dataset, graph databases excel at managing highly-connected data and complex queries. With only a pattern and a set of starting points, graph databases explore the neighboring data around those initial starting points — collecting and aggregating information from millions of nodes (Nodes are the entities in the graph.They can hold any number of attributes (key-value pairs)called properties . Nodes can be tagged with label , representing their different roles in your domain. Node labels may also serve to attach metadata-such as index or constraint information, to certain nodes) and relationships — and leaving any data outside the search perimeter untouched.

2 Likes
#318

Excellent answers sir, well documented! Please keep them like that :muscle:

Carlos Z.

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

Faster, high scalability and availability, can handle large quantities dynamic of data, data can be inserted and updated on the fly, Simpler, Non- relational,

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

  2. 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 they doesn’t have constrains and doesn’t support joins so they have less functionality and more scalability.

  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
#320
  1. If we are dealing with huge amount of data, noSQL will scale better, also data can be inserted easily
  2. No, there are not such strict rules as in relational data-base has
  3. Scales better but has less functionality
  4. NO, SQL is the way to go
1 Like