SQL and Relational Databases - Reading Assignment

[Wxdoc]

1. Advantages of NoSQL vs SQL --;
   NoSQL has high scalability and availability and SQL is not.
   NoSQL can handle huge amount of data and SQL cannot.
   NoSQL has higher performance abilities than SQL.

2. NoSQL don’t need strict structure for it’s data there by contributing to it’s high performance.

3. NoSQL is easily scalable and faster in most operations but its functionality suffers as a result of no constraints and joins querying abilities. Rendering its data inconsistent and lacking integrity.

4. It is not a good idea to use NoSQL if you have important relationships to track. It don’t have the functionality to perform with the related querying abilities.

[Laclaire1]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   non-relational model
   Uses JSON
   High Scability and Availability
   Greater flexibility (used for web applications that can evolve quickly where it would be difficult to modify the stricer relationship model

2. Do you have to defined a strict structure for your data in NoSQL?
   No, the document model is more flexible. There are no constraints and joins are not supported.

3. What can you say about the trade-off between scalability and functionality in NoSQL?
   If you look at web applications, they need scalability. If they are successful the users can increase overnight to thousands, tens of thousands or even more. A relational model won’t be flexible enough to keep up with the changing requirements of a web application for which we cannot easily predict future requirements for data / fields needed.

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

[MarcAndre_Morissette]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   NoSQL `
   Non-relational
   Low cost
   Various kinds of NoSQL DB available
   Easily scalable
   No need for detailed DB structuring

SQL
Speed
Well defined global standards
Atomic transactions - Secure
No coding needed
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 is easy to scale up a simple structure with less relationships. The functionalities are not optimized because if the structure always change, it is hard to automate a strategy in functions. SQL stay the same in structured queries with a structured data.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No.

[Cryptoshi007]

@ivan

• What are some of the advantages of NoSQL databases compared to SQL databases?
  a: Good for handling large amounts of data, quick response for data retrieval, easy to scale.
• Do you have to defined a strict structure for your data in NoSQL?
  a: No, unlike SQL, you do not need tables and columns.
• What can you say about the trade-off between scalability and functionality in NoSQL?
  a: Functionality is less than what SQL provides you but the scalability is much easier as it allows handling of large amounts of data.
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  a: No, something like MySQL would be best to handle data that can help manage relationships.

*answer found underneath each question above

[ghiasi12reza]

1. Easy to scale and much faster than MySQL

2. No, You simply insert all the datas

3. It is much faster and more reliable for huge data inserts and more functionality .

4. No

[levinardo]

1. What are some of the advantages of NoSQL databases compared to SQL databases?
   NoSQL has high scalability and is much faster to configure when compared to SQL databases because we don’t have to pre-define structure and data format / relationships between tables.
2. Do you have to defined a strict structure for your data in NoSQL?
   Strict data structure is not required in NoSQL, in fact it can even change after the NoSQL has been setup.
3. What can you say about the trade-off between scalability and functionality in NoSQL?
   Depending on the purpose of the database, I would see the NoSQL as the lite database version where it doesn’t need to put constraints and complex relationships between various data sets. Meanwhile if I have data that I would need to perform many different types of computations between different data sets in different tables, I would not use NoSQL because it doesn’t have the JOIN.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
   If the relationships are so important to keep track off, Relationship Database is much preferred.

[Gus]

1. NoSQL database is highly scalable, they can be structured on the go as need arises and they are easier to manage in distributed systems.
2. When designing a NoSQL database, there is no need to define a fixed structure.
3. More structure provides more query alternatives and strict definition of relationships, but it deteriorates in performance. NoSQL databases provide more performance at the expense of lower functionality.
4. If your data structure needs strong and fixed relationships is not advisable to go with a NoSQL database structure.

[VanellaVader]

1. NoSQL has a greater level of scalability, it can use horizontal scaling to store data on multiple machines, allowing it to handle huge amounts of data which would be far less practical with SQL
2. NoSQL is designed to handle data that is semi-structured, allowing for a higher performance, but the lack of constraints and joints makes it less functional for using small, specific sets of data
3. The trade-off can be helpful when using larger sets of data that are less dynamic and specific and can be stored on multiple machines, but it is not so helpful for relational databases requiring more constraints
4. in this case, RDBMS would be more appropriate because these relationships require smaller, more specific and functional data fetching

[pmensonp]

1. In a NoSQL database, you are able to scale larger amounts of data. The Data does not have to be structured and does not change overtime. Constraints and joins are not required. Easily scalable. Low Cost.

2. No

3. You don’t have the relational functionalities of a traditional RDBMS but if you need to consistently update, change data types, along with scaling then its worth using NoSQL

4. No because the recipient or client may not be receiving the most consistent state of the data .

[sandGrain]

What are some of the advantages of NoSQL databases compared to SQL databases?
- can cater for unstructured data
- data structure can be changed easily … basically same object can have same or different set of attributes
- less planning required in database design
- scales really well

Do you have to defined a strict structure for your data in NoSQL?
- No. Not required. But always good to have a real good understanding of the usecase.

What can you say about the trade-off between scalability and functionality in NoSQL?
- data is not structured
- so if you have to query the data, then proper planning is required on how you will partition the data based on the application requirement
- redundancy can also be a trade off as the datbase is not normalized

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
- probably not
- but it all depends on the type of NoSQL DB we choose for instance Cassandra (Key, Value) database are good with relationships
- we can also use CosmosDB with Gremlin api … or perhaps Table api … but if we have choice between SQL or NoSQL for simple relations then definaltely SQL would be first choice

[javier_ortiz_mir]

• What are some of the advantages of NoSQL databases compared to SQL databases?
  It has better performance and scalability
• Do you have to defined a strict structure for your data in NoSQL?
  Not necessarily, you can directly start to store the data before you define a structure.
• What can you say about the trade-off between scalability and functionality in NoSQL?
  It comes at a less functionality price, as you cannot have constrains at the database level (for example, any number can be stored, even a huuuuge number which could put you at risk of spending too much at storage level) and Joins are not supported (whatever that is)
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  You can also use them, but it would be better to use a relational database or SQL database. Each to its own.

[crypto_j55]

What are some of the advantages of NoSQL databases compared to SQL databases?
Answer: No need to create tables, define schemas, setup data fields before inserting data, easy to scale, much faster for most types of operations, data is stored in JSON format which is more compatible with other applications, high availability as the DB auto-replicates itself regularly and any failure reverts itself to the previous consistent state.

Do you have to define a strict structure for your data in NoSQL?
Answer: No

What can you say about the trade-off between scalability and functionality in NoSQL?
Answer: NoSQL has high scalability which is great for data intensive applications. However, for applications that need high confidence in the integrity of data (like a banking app), SQL may be a better option as NoSQL has less functionality.

If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Answer: Likely a better option would be SQL.

[Albert]

1. High scalability, high availability, work with a huge amount of data.
2. No
3. NoSQL shows structured or semi structured data with less functionality and high performance.
4. No, better choice is SQL.

[Kim]

What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL database scales much easier ,is much faster and better for dealing with huge amounts of data.
Do you have to defined a strict structure for your data in NoSQL?
No you can insert, update on the fly with No SQL.
What can you say about the trade-off between scalability and functionality in NoSQL?
NoSQL has less functionality but higher scalability. Less functionality, because you can’t have constraints in NoSQL nor joins. These actions hinder the scalability of a database but via MongoDByou can impliment these functionalities at the application level.
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 another database model.

[klby]

1. NoSQL advantages are
   High scalability , because they use sharding (horizontal scaling) which
   High availability, it has auto replication feature so whenever there is a failure, the data replicates itself to the previous consistent state

2.We don’t need to define a strict structure since we don’t need the relations in noSQL

3. NoSQL despite its high scalability, it has less functionality compared to SQL

4. It’s not, because NoSQL doesn’t have the feature to relate one data to another

[Nida_Wilson]

1. You can insert, update data on the fly. Easy to scale and faster. Best when dealing with huge amount of data = High scalability and high availability.
2. NO
3. Scalability - Storing large volumes of data without structure, uses MongoDB.
   Functionality - NoSQL used for big data and real time web apps. Information stored and aggregate - a single record with everything about the transaction including delivery. A cluster of servers can be used to hold a single large database.
4. NO, In NoSQL - you don’t design your database based on relationships between data entities.

[JCrypto]

1. High availability and high scalability
2. There is no strict defines structure, data is updated as you go
3. So long as your data does not need to be structured you can use NoSQL for scalability
4. No. You should not use NoSQL

[BigBoi]

1. Low cost, less time setting up and optimising, scalable

2. No

3. I don’t really see it as a trade off. If you’ve done your due diligence on what you are trying to achieve and what you, staff and tech stack are capable of then you’ll chose one over the other as it fits your long term requirements.

4. No, RDMS

[elea]

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

NO SQL:
When relation between data is not important, its good to handle large volume of data, low cost, and no need to put time in structuring, coding in JSON

SQL:
easy to do queries, no coding needed, atomic and secure data.

• 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?
  When you want to opt for data storing solutions that handle large volumes of data and also data that is growing more and more, you better go for a scalable solution such as NO SQL, but its less easy to do queries for data and relations between them, as the data is not structured.
• If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  not at all

[dextro]

Reading Assignment: NoSQL Introduction

@ivan

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

NoSQL databases don’t require you to define tables, schemas, or data types before inserting data. Because NoSQL databases focus on the ability to insert and retrieve data, they often perform better than tradition SQL databases that are focused on data integrity and relationships. Also, horizontal scaling and high availability are core abilities of many NoSQL databases, making them ideal for working with large data sets.

@ivan

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

No. Generally you can “just start adding data” as a NoSQL database does not care about the structure of the data you add.

@ivan

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

While NoSQL databases are considered more scalable and performant for large sets of data, that advantage comes at the cost of functionality. For example, you can not limit certain fields to a specific type of data and you cannot join data across multiple tables. Those types of functions must be performed at the application level.

@ivan

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

No. If you care primarily about data integrity and the relationship of objects between one another a traditional SQL database is likely the better solution.