SQL and Relational Databases - Reading Assignment

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

Fast, flexible, can handle huge amounts of data, hence scalability. Horizontal stacking helps keep track of the order data came in. No SQL is good where the relationship between the data is unimportant. It’s good for unstructured data which may change its characteristics over time. It works where joins and constraints aren’t necessary. It’s great for data streams which are are growing fast.

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

No, which is the advantage as you can add different types of data as you go on.

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

Higher scalability less functionality.

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

No, SQL is much better.

1 Like
  1. NoSQL is scalable and can handle much faster operations. In NoSQL there is no need for creation of tables, schema defining, or setting data types to name a few, like in SQL.
  2. No. The data is ever changing and as that data grows can be scaled (sharding)
  3. NoSQL can be scaled vertically and horizontally as the needs/data change. SQL is less optimal in terms of data structure changes. No constraints and No joins support hinders the scalability of the DB, however functionality can be implemented at the application level.
  4. No
1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • High scalability
  • High availability
  • Handling large amount of data
  • No need to structure data (Can be usefull in some projects)
  1. Do you have to defined a strict structure for your data in NoSQL?

No

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

Eventual consistency is one of the concepts used in NoSQL databases to achieve high performance and scalability.
These advantages are bought by the fact that the stricter ACID consistency concept, which is common in relational database management systems,
is no longer guaranteed.

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

No

1 Like
  • What are some of the advantages of NoSQL databases compared to SQL databases?
    High Availability
    High Scalability
    Fast Response
    CRUD is managed effectively

  • 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?
    Scalability in NoSQL is quite easy compare to functionality and this is how:
    In NoSQL DB sharding is a means of attaining Horizontal Scalability by storing data in a partion way and maintain of order by just the addition of more machine therefore endless data can be stored
    Meanwhile
    Functionality of CONSTRAINTS and JOIN is not available in NoSQL but on the application level such as MongoDB you can implement such.

  • 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. NoSQL will be a better choice if data is large, relations not important, data is unstructured etc.
  2. No, that is one advantage.
  3. If you need relations SQL is to prefer but if you need a dynamic structure NoSQL is to prefer.
    Once you have decided on the structure in SQL it is expensive to adjust.
  4. In this case a SQL-DB is better.
2 Likes
  1. The main advantages are high scalability and high availability.
  2. No
  3. It’s quite significant and you would have to be sure about your needs.
  4. No
2 Likes
  1. Better scalability, faster operations.
  2. No.
  3. There’s less functionality in NoSQL database - data not structured and you can’t have constraints in that type of data base.
  4. No, the relational database will be a better choice.
2 Likes

1 High scalability and high availability.

2 No and this is one of the reasons you may want to use NoSQL DB

3 NoSQL DB offer more scalability paying less functionalities. The opposite for SQL DB

4 No, you’d better use a SQL DB

2 Likes

1 A graph is an abstract data type typically used to model data that contains objects (referred to as nodes or vertices), and some sort of relationship between those objects (lines or edges).

2 A relationship between nodes.

3 A node containing data

4 Graph databases provide a strong advantage over relational database systems for datasets that contain a large amount of relationships within the data.

2 Likes
  1. In NoSQL we don’t need to define the table and structure, just add the data and and update later.
    It is much easy to scale and has high availability.

  2. We don’t, it is flexible.

  3. SQL is more securem but NoSQL allows high scalability and data replicates itself to previous consisten state in case of failure.

  4. No, for sensitive information is better to use a Relational database (SQL) which provides consistency and integrity of data

1 Like
  • What are some of the advantages of NoSQL databases compared to SQL databases?
  1. Easily scalable, much faster in most operations, can insert and update on the fly.
  • Do you have to defined a strict structure for your data in NoSQL?
  1. No, a strict structure would prevent updates and changes made quickly.
  • What can you say about the trade-off between scalability and functionality in NoSQL?
  1. SQL - More functionality, Less performance
    NoSQL - Less functionality, High performance
  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  1. No, SQL is more secure for keeping sensitive or important data
1 Like
  1. Some of the pros in NoSQL databases are high scalability and high availability
  2. NoSQL does not require setting out a structure for its data
  3. NoSQL envisages lesser functionality and higher scalability and performance
  4. NoSQL is preferable where there are big volumes of data and relationships are not important
1 Like
  1. Can store large amounts of data, don’t need a defined structure and schema before implementation, highly scalable through horizontal scaling and high availability due to auto replication.
  2. No. You can insert and update data on the go.
  3. The more scalable a database is, the less the functionality, the more functional, the less scalable. This is due to constraints and joins in SQL databases which make it easier to query data thus making more functional. Without constrants and joins databases are more scalable, but have less functionality without these properties.
  4. Probably not as NoSQL databases are not relational, thus if relationships are important a NoSQL database would not be optimal.
1 Like

1.- High scalability and High Availability
2.- No in NoSQL, but in RDBMS yes.
3.- NoSQL do not support constraints and joins.
4.- It is not, since NoSQL does not support constraints and joins.

1 Like
  1. Advantages of NoSQL over SQL is scalability and high availability.
  2. There is not strict structure in NoSQL.
  3. It all depends on what type of application you are running and what type of data is being stored. If it is large amounts of data that does not connect with other data NoSQL is recommended.
  4. NoSQL is not a good idea to track important relationships between your data.
1 Like
  1. High scalability and availability versus and SQL

  2. No you can add more data on the fly

  3. You have less functionality however you have improved scalability

  4. No RDBMS would be better

1 Like
  1. Advantages of NoSQL databases:
  • scalability;
  • faster operation for huge amount of data;
  • less database administration;
  • cheaper storage.
  1. You don’t have to define a strict structure for the data in NoSQL.

  2. NoSQL provides less functionality but gives more performance.

  3. It is a good idea to use a relational database instead of NoSQL to maintain data’s important relationships.

1 Like
  1. The main advantages of NoSQL DBs, compared to SQL DBs, are their high degree of scalability and flexibility.

  2. No, you don’t; i.e. in NoSQL you can adjust the structure of your data as the project evolves.

  3. The tradeoffs when choosing a NoSQL DB instead of an SQL DB are uniformity (clear/defined data structure) and security (atomic TXs)/ data integrity.

  4. No, not if your data has important relationships. In this case an SQL DB (relational DB) is the path to explore; and if in doubt, the DB type to go for.

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    A. In NoSQL, you don’t have to worry about crating tables like SQL and you can insert and update data on the fly. Also NoSQL is easy to scale and is faster and can handle huge amount os data compared to SQL.
  2. Do you have to defined a strict structure for your data in NoSQL?
    A. No.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    A. The main trade-off is ACID properties (Atomicity, Consistency, Isolation and Durability).
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    A. No.
1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • easy to scale
  • much faster for certain operations
  • better choice when dealing with huge amounts of data
  1. Do you have to defined a strict structure for your data in NoSQL?
    There is no strict strucure, you can change the structure on the go while adding your data in the db.
  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    If there are no relationships in your database and there is just huge amount of data that keeps increasing, needs to be stored and needs to be retrieved fast, having less functionality does not seem to be a big impediment. One of the 2 types of databases should be chosen to best fit the project the database is required for.
  3. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    When having important relationships that you need to track, it is recommended that you use an SQL database (RDBMS)
1 Like