SQL and Relational Databases - Reading Assignment

[deathbeach]

1. Many developers know how to use it, Great for relational data, Secure
2. No
3. Easy to scale, faster, great for large amounts of data. Adaptable.
4. No, it is better to use SQL

[jernejb]

1. No need to predetermine data type, table, define schema. NoSQL databases are also easy to scale and faster (high scalability, high availability).
2. No.
3. NoSQL databases are easier to scale (high performance, more data), but they offer less functionality.
4. No, relationships are one of the key features of SQL databases.

[CryptosaurusRex]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
Faster, highly scalable, no need to design a complex structure at the outset

2. Do you have to define a strict structure for your data in NoSQL?
No it isn’t necessary

3. W hat can you say about the trade-off between scalability and functionality in NoSQL?
Some of the improved functionality of NoSQL comes at a cost. You can’t have data constraints and JOINs are not supported. These are things that make a database less scalable.

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

[Tristan]

QNS 1. What are some of the advantages of NoSQL databases compared to SQL databases?
ANS: The advantages are it is faster, more scalable and does not required a structure from the start.

QNS 2. Do you have to defined a strict structure for your data in NoSQL?
ANS: Nope, it is not necessary.

QNS 3. What can you say about the trade-off between scalability and functionality in NoSQL?
ANS: The tradeoff will be not being able to have constraints and Joins are not supported. These actually hinders the scalability of a database.

QNS 4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
ANS: No, SQL will be the better choice to manage important data relationships.

[KcDevDude]

1. Some advantages are you do not need to define the data before inputting which makes NoSQL much more scalable than SQL databases. In SQL databases the consistency and integrity of the data is strictly enforced so it could make significant data overhead and slow the data response times.

2. No it can be semi structured.

3. The trade off is that NoSQL is highly scalable and is high performing. You can’t have constraints in NoSQL so it loses some functionality compared to SQL databases.

4. Definitely not.

[LMC]

@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. Advantages of NoSQL are scalability, performance, not much need for structure, lower cost
2. No
3. NoSQL is not as complex and can handle large amounts of data flexibly, therefore it is said to be more scalable but lower in terms of functionality.
4. No. SQL will be better.

[RBIG]

1. NoSQL databases are highly scalable and much faster. They can process much more data and support data that is changing over time.
2. No, the data can be modified easily as the database evolves.
3. NoSQL is highly scalable but has less functionality to use the data contained. It is more commonly used to handle larger amounts of changing data.
4. No, SQL would be a better choice.

[Naomshka]

1. Faster operations, holding huge amount of data, lower cost

2. No

3. High scalability and less functionality than SQL databses.

4. No

[Anidez]

1. What are some of the advantages of NoSQL databases compared to SQL databases? High scalability, the property of growth in a Vertical and Horizontal way.
2. Do you have to defined a strict structure for your data in NoSQL? no, thats one of the characteristic of NoSQL, they don’t need to maintain their structure, this can change without loose integrity.
3. What can you say about the trade-off between scalability and functionality in NoSQL? More functionality less performance.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No, the confirmation of a successful transaction is posible in SQL, NoSQL don’t have this characteristic.

[Sergio_Garay]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   They are really easy to scale and they are much faster in most types of operations performed on a database. Is your best choice when you are dealing with a huge amount of data. 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?
   If you have a huge amount of data and the relationships are not so important then scalability should be more important than functionality, so NoSQL would be a better option than SQL

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

[FrinaDC]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   The main advantages are high scalability and high availability. You can handle a larger quantity of data in NoSQL databases. Also, the data is not structured and it is flexible to change over time.

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

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   The scalability in NoSQL is coming at the price of less functionality. It is simpler to store the data, as there is no need for a stricter structure, which could lead to certain inconsistencies.

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

[Crypto_Craven]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   No SQL is more performant and doesn’t require a Schema
2. Do you have to define a strict structure for your data in NoSQL?
   No, the structure is provided by the object being stored
3. What can you say about the trade-off between scalability and functionality in NoSQL?
   No SQL doesn’t have the same functionality as a rational database for example:

• NoSQL doesn’t allow constraints such as required fields or relations which protect the data integrity
• NoSQL doesn’t allow table joins

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   No as stated previously there would be no constraints to protect that relationship integrity and this would likely lead to incomplete datasets

[Tomahawk]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
They are faster, they are scalable, they can handle huge amount of data, they can be mutable

2. Do you have to defined a strict structure for your data in NoSQL?
No you don’t have to since data can be changed anytime.

3. What can you say about the trade-off between scalability and functionality in NoSQL?
NoSQL is more scalable but has 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, if you have important relationships between data then SQL is better choice.

[Sgtcrypto]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   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?
   The trade off is worthwhile where large amounts of unstructured data need to be quickly stored and retrieved and where relationships between data are not important.
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 an SQL database.

[dgbit]

1.It has a better performance than relational databases. It can scale via sharding. It is easier to store data (json compatible).
2. No, you can store data as it is.
3. It is better to store huge amount of unstructured data that does not need to be related somehow, but it is worse when relationships need to be stablished in order to analyze data.
4. No, for that purpose sql.

[lordkalvin]

• What are some of the advantages of NoSQL databases compared to SQL databases?
  • high scalability
  • high availability
• 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 is easily scaled
  • NoSQL handles common operations much faster than SQL
  • NoSQL is good for horizontal scaling which is easier to implement than vertical scaling
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  • no

@LORDKALVIN

[MattL]

1. High Scalability and Availability
2. No…can be semi structured
3. The higher functionality and speed need the less scalable it will be. A trade off
4. No…SQL is best for relationships.

[Danielito]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Scalability, for huge amount of datas, not a fix structure, constraints and joins support is not required

2. Do you have to defined a strict structure for your data in NoSQL?
   No, thats one advantages of a NoSQL

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   Scalability is very high, but with this in reverse comes the lower functionality (no constraints and joins)

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

[Lumin8Crypto]

• What are some of the advantages of NoSQL databases compared to SQL databases?
  High Scalability - It is easier and quicker to scale to multiple servers.
  High Availability - Because it is easy to scale on multiple servers, it will also increase the availablity of the serer.

• Do you have to defined a strict structure for your data in NoSQL?
  No the data is more adhoc instead of having a formal data structure.

• What can you say about the trade-off between scalability and functionality in NoSQL?
  NoSQL does not allow for constraints (AKA the SQL Where Clause) and does not allow for joins. IE no one to one, one to many or many to many relationships.

• 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 include relationship functionality.

[Denzel]

1.- High scalability, high availability, high compatibility.
2.- No.
3.- Some features compensate others.
4.- No, it is not.