SQL and Relational Databases - Reading Assignment

1- They offer flexibility of structure, structure can be changed at any time and handle huge amount of data They are more scalable and fast. NoSQL store their data in JSON format, which is compatible with most of the today’s world application.

2- No

3- The trade off is that a NoSQLs is less secure because it is easier to add data centers and new computers to the database. And that means that the info needs to be synced to all the computers, data centers and this take milliseconds and during that time the information might be outdated, not consistent.

4- Not really because the information is more secure and accurate in SQLs therefore SQLs should be used.

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL databases offers speed, high scalability and high availability. They can also handle a large amount of data.

  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?
    In NoSQL databases the scalability and the functionality are higher than in a SQL database.

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

1 Like
  1. The biggest advantages of NoSQL database is the performance. With performance I mean faster, more scalable. They have also a higher availability. Furthermore, you don´t have to think about any complex rules or structures how your data should be define. You can store your data instantly and updated it how you want.

  2. No it is not required. You can start instantly.

  3. With NoSQL database you have a high scalability, because of sharding. Sharding allows NoSQL to handle a huge amount of data. NoSQL is also capable of dealing with data in a very efficient manner when the data is growing over time. But this concept has also less functionality , because there are no constraints (no rules or definition what should not happen for example), no joins (which mean no relationships between the data). But with MongoDB you can add these features on the application level.

  4. At first sight no, because NoSQL cannot handle these relationships. But when you need a high scalability, then you can use NoSQL in combination with MongoDB, because you can add these features on the application level (if I understood it correctly).Would be nice if someone can verify it.

1 Like
  1. really easy to scale and faster in operations. High Scalability and High Availability
  2. No
  3. Structured data that provides more functionality gives less performance
  4. No use SQL DB
1 Like
  1. Some advantages are in terms of the ability to handle change within data over time, greater scalability, ability to manage more data and lower costs.
  2. It is not mandatory, as it can handle both structured and semistructured data.
  3. It is highly scalable and performing but its functionality level is low. This because NoSQL does not implemente Joins and constraints.
  4. No, it is not the best idea. It would be better to use a relational database such as SQL.
1 Like
  1. NoSQL can handle vast amounts of data
    It can scale very easily if required.
    It has a lower overhead cost.

  2. No

3.If relationships between your data is not important then NoSQL would be recommended because it is cheaper to run and is more scalable… But if data relationship is needed SQL is better as it is much more functional.

4.No

1 Like

Hi,
1, Faster because of lack of detailed structure, more scalable, high availability
2, No you. you can insert data/update data right away
3, In other to achieve scalability in NoSQL we discarded some functionality- Constraints and Joins are not supported by default. data is not structured.
4, no it’s not. NoSQL does not keep track of relationships.

1 Like
  1. NoSQL database is that they are really easy to scale and they are much faster in most types of operations that we perform on database. In relational database you need to create the table, define schema, set the data types of fields etc before you can actually insert the data. In NoSQL you don’t have to worry about that, you can insert, update data on the fly.

2.You can insert, update data on the fly.

3.NoSQL came into existence because the databases at the time couldn’t handle the scale required. The rise of this new generation of data services solved many of the problems of web scale and rapidly growing data sets when it was created more than a decade ago. NoSQL also offered a new, cost-effective method for cold storage/occasional batch access for petabyte scale data. However, in the rush to solve for the challenges of big data and large numbers of concurrent users, NoSQL abandoned some of the core features of databases that make them highly performant and easy to use.

4.No

1 Like

Most importantly, NoSQL overcomes the limitation of relational databases.
NoSQL is easy to scale, and the speed of operations are very good. It has high availability.
2.
With NoSQL you can insert data right away, without the need of creating different tables, data types and other structures.
3.
Less functionality because there are no constraints in NoSQL, and joins are not supported.
Easier to scale because horizontal scaling can handle huge amount of data.
4.
Not really, better to use SQL if relations are included.

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases? You can insert and update data, easy to set up, faster processing and good when dealing with huge amounts of data.
  2. Do you have to define a strict structure for your data in NoSQL? There is no need to define a strict structure for your data since it can be added and updated as needed.
  3. What can you say about the trade-off between scalability and functionality in NoSQL? For NoSQL the main advantage is high scalability and high availability. There is structured or semi structured data that has less functionality and high performance. NoSQL can’t have constraints and 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, you should not use NoSQL if you need to keep track of important relationships.
1 Like
  1. They are really easy to scale and they are much faster in most types of operations that we perform on database. High scalability and high availability.
  2. NO
  3. NoSQL has more scalability but less functionality For example you can’t have constraints in NoSQL and joins are not supported.
  4. No it is needed a relational database (SQL)
1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    They are easier to scale and much faster. It is the best choice when you need to deal with a huge amount of data.
  2. Do you have to define a strict structure for your data in NoSQL?
    In NoSQL we do not have to worry about tables, schema’s, data types, etc. Data can be inserted and updated on the fly.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL scales better 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, SQL would be better.
1 Like

NoSQL Introduction – Reading Assignment

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

When your data is changing continuously or even over time and you have to continue to update your data would be the need for scalability and the you would have to trade off using joins for relational queries, or in no need of constraints .

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

No

1 Like

NoSQL `
Non-relational
Low cost
Various kinds of NoSQL DB available
Very easy to scale
No need for detailed DB structuring

SQL
Fast
Most common among devs
Atomic transactions
No coding needed

  1. No, since data is most likely going to change regularly, there is no need for a SQL Structure.

  2. No SQL is much better for scaling but has less functionality.

  3. No, SQL Databases are better to keep track of important relationships.

1 Like
  1. NoSQL databases have more scalability meaning that when you have a constant stream of data it is easy to scale the database to handle the data.

NoSQL databases store their data in JSON format which most applications also do as well.

NoSQL has higher performance based on the processing power used. This means from a company perspective they are cheaper to run efficiently.

  1. No you do not

  2. In noSQL you are getting high scalability and performance at the expense of functionality. noSQL are able to store and track huge quantities of data at the expense of not being able to track and store the relationships between the datas.

  3. Not at all. Use SQL instead.

1 Like

1)What are some of the advantages of NoSQL databases compared to SQL databases?
Highly scalable and highly available
2) Do you have to defined a strict structure for your data in NoSQL?
Nope
3)What can you say about the trade-off between scalability and functionality in NoSQL?
They are highly scalable but less functional on the other hand SQL databases and less scalable but more functional
4)If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No

1 Like
  1. Compared to SQL databases, NoSQL databases offer:
  • better performance when using large amount of data
  • no need to structure the data
  • better scalability
  1. NoSQL does not required a data structure before creating entries in the database
  2. NoSQL is more scalable and can able larger amounts of data. The trade-off are the more limited functionalities that SQL has like constains and joins
  3. It would not be a good idea to use NoSQL if data had important relationships
1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

High scalability and high availability

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

No, In NoSQL you can insert, update data easily.

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

While NoSQL allows for high scalability it prevents constraints and Joins which can limit functionality.

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

No, you are better off going for an SQL database

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

Lower cost and more scalable for large quantities of data that are not relational in nature

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

  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    Less functionality while higher performance.

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

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL - Better Performance with large dataset, scalable, and doesn’t required a data structure.
    SQL - Atomic, Secure, defined data structure

  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 are highly scalable and provide excellent performance benefit especially when dealing with high volumes of data. Due to the fact the data doesn’t have structure.

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

1 Like