SQL and Relational Databases - Reading Assignment

[abnrgr99]

1. stores and retrieves large amounts of data and is easier to scale when data as grows
2. no
3. when large amounts of unstructured data need to be quickly stored and retrieved and where relationships between data are not important
4. no

[bars]

NoSQL Introduction - Reading Assignment

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

• In NoSQL you can insert, update data on the fly
• Easy to scale
• Much faster
• If you have huge amounts of data NoSQL is your best choice. High scalability and high availability

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

No, you can change it as you go.

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

As I understand it if you don’t need relationships between the data you store. You will get more scalability and performance. But trade-off functionality.

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

Nope

[Mesiah]

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

A: You can insert, update data on the fly, easier to scale and they are much faster in most types of operations that we perform on database.

A: no it can worl off of the structure already in place

A: NoSQL has more scalability and performance but less functionality

A: No it is better for large amounts of data storage and it changes over time

[jopo]

faster queries, huge amounts of data can be handled, easier to scale, easier to handle if the data structure will be changed

No

Due to the high scalability some functions like “join” do not work on the database level.

No. Use a SQL db instead.

[AF90]

1. NoSQL is scalable and high performing.
2. No, you do not need to define a strict structure for your data with NoSQL.
3. NoSQL can handle much larger quantities of data and is adaptable in comparison to RDBMS, however the trade off is that you cannot use supports. Having said that, supports can be implemented at application level.
4. No, it is probably best to go with an RDBMS if the relationship between data is important.

[Enrique]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Easy to scale, faster operations, better dealing with 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?
   NoSQL does not support joins, so it is less functional but has a higher scalability
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   No

[DreamtGalactic]

1. You do not have to create infrastructure of the database, you can simply insert and update it whenever you want. They also have improved scalability and speed, and are better for dealing with vast amounts of data than SQL databases.

2. You do not need to define a strict structure for NoSQL.

3. With NoSQL horizontal scaling is easy through database systems like MondoDB, which means that it is not difficult to handle large influxes in data entering the database. The tradeoff however is functionality, meaning that you “cannot have constraints in NoSQL,” and “joins are not supported in NoSQL.”

4. If you need to keep track of relationships in your data NoSQL is probably not the optimal database type for you, since it is not a relational database. Instead, you should use SQL, since it is a relational database.

[Neeraj_Nerlekar]

1. The main advantages of NoSQL databases compared to SQL databases are high scalability and high availability.
2. No.
3. The following are the trade-off between scalability and functionality in NoSQL. You can’t have constraints in NoSQL, and joins are not supported in NoSQL.
4. No

[JBrewer]

1 - sharding for horizontal scalability; availability via auto replication in case of system fialures
2 - nope, a defined schema is not needed
3 - you need to really understand your needs and app requirements and data load and types and relationships before selecting which route to go. if you don’t understand the trade-offs you will likely incur big costs down the road
4 - no

[cryptopunk]

1. faster in handling huge data, the structure and scheme of data has not to be structured in the beginning and remain the same, data is stored in json-format, which is widely used in applications and data exchanges
2. no ; and it can be changed/adjusted over time
3. one choses nosql database because your data is better fitted than for a relational database. but if you need functionality, you can still implement it on application the application level
   4)then you are better off with a relational database

[SGB]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Performance, scalability, minimal setup (data schema does not have to be defined), work with HUGE amounts of data, a lot work with JSON a data format native to modern app development.

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’s scalability is the most attractive option when needing to store huge amounts of data, that doesn’t necessarily adhere to a consistent structure, and doesn’t need to be related.

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   Probably not, an RDBS SQL database supports data relationships very easily and intentionally

[aryakrishna]

1. High Scalability and High Availability
2. the structure does not really need to be strict
3. its a win-win solution in regards to the needs of exact purposes and priorities
4. Not a good idea if the relationship of the data is important, but if its not, MongoDB let the relationship works on application level

[SatoshiOkoto]

• What are some of the advantages of NoSQL databases compared to SQL databases?
  You dont need a data structure to store the data.
  You can store a massive amount of data.
  Its faster.
• Do you have to defined a strict structure for your data in NoSQL?
  No you dot have to.
• What can you say about the trade-off between scalability and functionality in NoSQL?
  No SQL is great for storing huge amounts of data but it is not good for finding relationships between the data.
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  That will not be a good idea.

[MartinAxel]

@ivan

• What are some of the advantages of NoSQL databases compared to SQL databases?
  It is fast, scalable, it has a simple database structure, it can store a lot of data and has low operational costs.

• 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?
  It is highly scalable but has a low functionality. So if you require less structured data but larger amounts, then NoSQL is your choice.

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

No, you should use a SQL database.

[Fabiana]

1. NoSQL databases have high scalability, manage huge amount of data and data ca be added and updated on the fly.

2. No, there is not a defined strict structure.

3. NoSQL are less functional but good to use when large amounts of unstructured data need to be stored and the relationships among the data is irrelevant.

4. No, NoSQL is not a relational database.

[Calle_Jansson]

1. Advantages of NoSQL is that it is quicker, handles huge amounts of data and has much greater scalability.

2. No you do not. Joins and constraints support is not required.

3. When you need to store huge amounts of data but the relationship between the data is not as important.

4. No it is most definitely not.

[JustMichael]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   Easy to scale and they are much faster than SQL dbs
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 tradeoff for scalability is in the need for NoSQL systems to give up ACID properties, more precisely the A, C, & D (Atomicity, Consistency, & Durability) - NoSQL must sync all nodes.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   No

[Namefake]

1. faster, easier to handle big amounts of data, higher scaleability, no structure needed, higher availability
2. No
3. NoSQL has a higher scaleability, but less functionality. Joints are not supported und you can‘t have constraints
4. No. It this case it is better to go for a RDBMS

[jdbarrancs]

1. Some advantages of NoSQL over SQL databases are high scalability and high availability.

2. You don’t need to define a strict structure for your data in NoSQL.

3. I can say that the trade-off between scalability and functionality in NoSQL is worth it if your data doesn’t need much relation between them.

4. In the case that your data has important relationships that you need to keep track off, I think it’s better to stay with RDBMS.

[CryptoRealNews]

1. NoSQL databases have better scalability and performance compared to SQL and do not require strict data structures

2. NO (but can be done at application level if required)

3. NoSQL trades some functionality of SQL to achieve better scalability

4. No, probably not the ideal db to use for important relationships.