SQL and Relational Databases - Reading Assignment

[DaanBoshoven]

1. No need to define schema, create table etc
2. No you don’t
3. Very limited in NoSQL
4. No

[kwaben]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Faster, Scalable, non restricted
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?
   When relationships are not important, data is large and unstructured and not demanding any in-built functionality the noSQL is best
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   No

Don’t forget to leave your answers

[Mohamed_Farah]

1. • Easier to scale.
   • Faster in most types of operations.
   • No need to define data structure, create table, define data types.

2. No

3. NoSQL provides scalability and availability of data at the cost of functionality.

4. No

[Murisoja]

@ivan

Welcome to the discussion about this reading assignment.

Leave your answers to the questions below in this thread. If you have any questions or you want to discuss something connected to the assignment feel free to do it in this thread as well, but please everything to the topic.

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 has better scalability, if lot data comes in
2. you can modify as you go
3. not as secure, it is reasonable to use NoSQL for database for high scalability.
   High availability, in the case of any failure, data replicates itself to the previous consistent state.
4. no

[J_Ri]

1. There are more performant, highly scalable, more flexible in the structure
2. No, the structure is not important
3. NoSQL are less functional than an SQL database because you can use join functions and constraints but on the other end there are much more scalable. So if you have a lot of data to handle and relationships are not so important, then you should use a NoSQL database.
4. You should better go with an SQL database

[Crypto_PONY]

1. Advantages of NoSQL over SQL DBs include;

• requires less structuring
• can handle more data

2. No. Data can be inserted and updated on the fly(due to JSON format of storing data)

3. Scalability is prioritized over functionality; NoSQL is more suitable for huge streams of data with changing variables.

4. No, SQL databases are more suitable for establishing important relationships in data.

[Monarcha]

1. NoSQL databases offer more scalability and higher availability
2. No
3. NoSQL has the advantage of better scaling and performance, but this comes at the cost of less programmability hence functionality.
4. No, it is better to use SQL for relational data.

[supertramp007]

1. What are some of the advantages of NoSQL databases compared to SQL databases? You can update data on the fly without having to create the table, define schema, set the data types of fields etc before you can actually insert the data. 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? No
3. What can you say about the trade-off between scalability and functionality in NoSQL? Scalability is easily achieved by scaling horizontally.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? no

[Haseley]

1. Some advantages of NoSQL DB’s compared to SQL DB’s are that they can scale up faster and easier, and also don’t have to be completely structured before using them (You can use them on the fly)
2. No you do not have to define a strict structure for your data in NoSQL, this DB type is especially good at easily upscaling and for holding large amounts of data (where the data does not have to go extensive relational in its functionality)

3)While the NoSQL can handle some relational activities, they are primarily designed to handle large data banks of mostly non relational data dumps (eg weather condition data added every minute, etc)
If you have large amounts of data where the data can be relationally handled by external applications then the NoSQL would be a good choice.

4)If you need a constantly queried database where relational data is often needed to be acquired, then an SQL based DB should be the preferred choice, even if you have to have a more difficult vertical upscaling of your DB needs.

[zozaa]

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

They are more easily scalable and adjustable. They do not require preparation and predefining data fields and sets - data can be inserted and organized along with the operations/ proces.

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

No, not in advance. And in NoSQL data structure can be altered on the way.

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

The tradeoff for using a NoSQL (gaining in scalability and performance/ speed aspects) is loosing some of the funcionality and ability to managing more complex data relations that need stricted rules.

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

If there are important and complex relationships among data entries it is more relevant to use SQL (a relational database management system) rather than NoSQL, because it is designed in a way to handle and secure these data relationships.

[MarkusJohansson]

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?
   NoSQL databases doesn’t have constraints and doesn’t support joins so they are 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

[Ozarkshrub]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   A. NoSQL can grow with the large data increases. Also, it works much faster than SQL

2. Do you have to defined a strict structure for your data in NoSQL?
   B. No, its a receiving dump for data.

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   C. they generally run in inversely proportional directions, what you gain in scalability you lose in functionality.

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   D. No, SQL is what you would use for info that requires functionality.

[Aleksander]

1. NoSQL data bases advantages:
   a. doesn’t need preparation works or pre-thinked structure. U can insert data from very start. So it is faster. (SQL need to be projected and built first, before U insert any data)
   b. high scalability, so U can work on huge numbers of data and U can scale the data base on the way of growth (SQL puts more effort to keep the base secure, so it may proces large data slower)
   b. high availability (NOT CLEAR IN THAT ARTICLE) I would say it is easy to gather all data U need as it’s structure is simply so machine read data fast.

2. No. It is one of advantages of horizontal structure: U can work on it from very beginning and scale it through growth.

3.In NoSQL databases U get higher scalability, U can work on large data, continously coming in large amounts, but the trade off is functionality, as U have less relations in the structure.

4.No, because NoSQL is not a relational database. Better to use RDBMS.

[OmeOmy]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   NoSQL databases are scalable, low cost, Able to store 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?
   Structure for a database reduces performance. Therefore a database like NoSQL will be quicker and able to process large volumes of data.

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

[Rob_Kammerer]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Higher scalability and better performance

2. Do you have to defined a strict structure for your data in NoSQL?
   no and you can change or add over time

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   RDBMS: It is a structured data that provides more functionality but gives less performance.
   NoSQL: Structured or semi structured data, 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?
   When reltaionships are important it is better to use a RDBMS data base because NoSQL does not have constraints and do not support joints

[Restford]

1. scalability, better performance, high availability.

2. No

3. If you want immutability, joins and atomic actions, go with SQL, otherwise if the data keeps changing, updates are needed and so on go for noSQL.

4. No, unless some other functionality is desired which SQL does not provide

[Acex13]

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

Extremely scalable and changeable, due to sharding and vertical scaling, which allows for the faster performing of operations with extremely large amounts of data. Data restores to most recent state on power outage, so no significant data loss or corruption.

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?

Very scalable for basic data feeds and a lot of data but not functional for complex data relationships requiring greater integrity and security, joins or constraints at database level.

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

No.

[Allistair_Trent]

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

The main advantages are high scalability through vertical and horizontal scaling and high availability because in case of any failure data replicates itself to the previous consistent state.

• 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?

NoSQL has 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. NoSQL does not allow you to set relationships in the same way as SQL

[Cecilia_Machado]

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

• Easy to scale.
• Much faster in most type of operations.
• Is the best choice when you are going to use a huge amount 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?
   RDBMS provides more functionality but less performance.
   NoSQL: Less functionality and high performance. 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?
   No, because you can´t use JOINS.

[Divij_Dawar]

1. It’s easier to scale a NoSQL database.
2. No.
3. When you use a NoSQL database you are trading off relationships and performance for scalability and functionality.
4. No.