SQL and Relational Databases - Reading Assignment

[D1alZer0]

1. NoSQL are really easy to scale and they are much faster in most types of operations that we perform on database; they also handle very large amounts of data more effectively than SQL.

2. When using NoSQL, you insert and update data on the fly, without any predetermined structure.

3. NoSQL offers less security than SQL, but when dealing with huge amounts of data, the scalability and functionality are worth the trade off.

4. Absolutely not.

[Wade]

1. easy to scale and more available. Very good at handling large amounts of data when the relationship between the data is not top priority.
2. No- NoSQL is more fluid where predefinition of system is not required.
3. The lack of functionality in certain tasks can be overcome in some way by implementing the functions on an application level.
4. No probably not.

[Tesla]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   You do not need to structure your data before entry, allows for data to change over time, and NoSQL can handle large 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 is less structured there for it is more scalable but less functional.

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

[Sherms]

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

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?
   It’s no trade off. NoSQL is used for high data with know relationships. And MongoDB has a feature that can recreate data if lost so at this time I see no trade off

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

[Shah]

Some of the advantages of NoSQL databases compared to SQL databases is data processing speed and ability to update data as its come without having to define into different tables.

No strict data structure is required in NoSQL.

NoSQL offers less functionality however is easier and cheaper to increase the scalability, while in SQL databases you have low scalability and high functionality. Inability of joins and constrains hinders scalability of NoSQL.

[katarzynagr1]

1. NOSQL

• no need of structuring
• more scalability when amount of data is growing
• holds much more data than SQL
• faster

2. No need to structure NoSQL data

3. NoSQL database has less functionality but higher performance. It is good when we need to store large amount of unstructured data but relations between data is not that important.

4. No, for relation purposes SQL is much better.

[Byron]

1. One of the advantages of NoSQL databases is that they are really easy to scale, so the main advantages are scalability and high availability.

2. No you do not have to define strict structure but it can to be semi-structured

3. Scaleable less structured data will help you help you retrieve more data constantly in your database with high a performance rate, the trade-off with functionality is that it is more structured but performance is low

4. No I would use a RDBMS which is a more structured data application

[BradCook]

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

Answer: The main advantages are high scalability and high availability.

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

Answer: No

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

Answer: what’s missing in functionality is:

1. You can’t have constraints in NoSQL

2. Joins are not supported in NoSQL
   However, in MongoDB, you can implement 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?

Not if you need to keep track of them at the database level, and your structure is constantly evolving and changing.

[matty.t]

1. High scalability and high availability
2. No
3. You get less functionality when you use NoSQL.
4. No, it is not a good idea

[Cobrati21]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Advantages of NoSQL data bases are the scalability and the high availability.

2. Do you have to defined a strict structure for your data in NoSQL?
   You do not have a strict structure for your data, which allows for data to be updated as required.

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   According to the article, the more scalability and performance the less functionality. The article goes on to say that you can implement these functionalities at the application level, or how your particular project requires.

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   If important relationships with your data must be maintained, NoSQL may not be suitable for use in your project.

[Dreamer]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Answer - The main advantages are high scalability and high availability.
2. Do you have to define a strict structure for your data in NoSQL?
   Answer - the strict and hierarchical structure is not that important in NoSQL, therefore, there is no need to define a strict structure for your data in NoSQL.
3. What can you say about the trade-off between scalability and functionality in NoSQL?
   Answer - NoSQL offers structured or semi-structured data thus offering less functionality but high performance.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   Answer - No, in this case, it is not a good idea to use NoSQL. SQL type of database would be a better fit.

[soko]

What are some of the advantages of
NoSQL databases compared to SQL databases?
When you with data want to measure something, where
there is a lot of data streams like “checking” the
weather, and sensors are collecting data where it does
not need to be precise, then NoSQL is a good choice.
Also when it comes to scalability. And when it’s not relational.
NoSQL is also more flexible.

Do you have to defined a strict structure for
your data in NoSQL?
Not as strict as in SQL. In SQL you first make a structure of data
and then you process the data.

What can you say about the trade-off between
scalability and functionality in NoSQL?
NoSQL is easy to scale and it is high availability.
And is a good choice when dealing with a lot of datastreams.
Although there a less functionality.
NoSQL is good when the data is changing over time.

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

[Phoenix]

@ivan

• What are some of the advantages of NoSQL databases compared to SQL databases?
• Do you have to defined a strict structure for your data in NoSQL?
• What can you say about the trade-off between scalability and functionality in NoSQL?
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?

1. NoSQL databases are better for handling large streams of data than SQL databases. NoSQL databases are also more scalable and faster than SQL databases and are simpler to structure.

2. no

3. The scalability of NoSQL databases comes from their ability to store and retrieve large streams of data as well as the ability to add new hardware easily, as needed, but the trade off is that you lose the relational functionality of SQL databases.

4. No, you would definitely want a relational database (SQL).

[Thijs.Smit]

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

• High scalability
• High Availability

choose when:
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.

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?
   It’s less relational and has no joins or constraints. Those kinds of functionality hinder scalability
   So NoSQL is therefore more scalable

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   I don’t think so if there are many different relationships

[sajede.k]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   you don’t have to worry about structure, you can insert, update data on the fly
   high scalability
   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?
   NoSQL has high performance and scalability but it doesn’t support joins so the choice depends on the application.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No, it’s not good for relation and the security is not high

[Nicksta]

1. The main advantages are high scalability and high availability.
2. No that is not needed. This SQL structure actually diminishes the scalability and availability advantages
3. less functionality more scalability
4. No, a SQL database would be better

[tuchtech1]

What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL DBs can handle huge amounts of data, are easy to scale and have readily available data.
Do you have to defined a strict structure for your data in NoSQL?
Nope.
What can you say about the trade-off between scalability and functionality in NoSQL?
If creating data relationships is the goal then SQL is the way to go. If it’s lots of data and has easy to grasp relationships then NoSQL may be best.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Most likely not, but if the number of data fields is small NoSQL could work

[itraben]

1. Scalable, fast, large data storage, doesn’t need detailed structuring.

2. No, you don’t need a strict structure for NoSQL data.

3. The trade off is in NoSQL’s favor when there is lots of unstructured data that needs to be stored quickly.

4. No, having lots of relationships means it’s usually better to use SQL.

[abbateslam]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   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?
   Less functionality and high performance.

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

[Uyan]

1. You might consider using NoSQL (Not Only SQL) databases when:

• You want to store huge amounts of data
• Relational data is of little importance
• The data can exist in an unstructured state
• You want to constantly update the data
• Your database needs to be continuously expanded

2. You do not have to define a strict data structure when using NoSQL.

3. SQL has high functionality but low scability/performance.
   NoSQL has low functionality but high scability/performance.

4. NoSQL is a poor choice of database when you have important relational data that you want to store.