SQL and Relational Databases - Reading Assignment

1.What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL handle huge amount of data

  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?
    its better to use NoSQL when you have huge a mount of data that you quickly have to store but relationships between data should not be important.

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

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High scalability.
    High availability.
    Less expensive
    Fster to process.
    More on performance.

  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?
    Becuase you donn’t need to define a structure in NoSQL, that is why it is more scalable but less secure.
    Thus it can handle higher voulum of data. Though it is less secure, lost data can be easily retrieved form the previous state.

  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. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL databases are better at dealing with big amounts of data, they are easy to scale and much faster in most types of operations.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, there’s no need for that.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL has the ability to handle large amounts of data but we can’t have constraints and joins are not supported in comparison with SQL data bases

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, we will use SQL as we value data consistency over transaction speed

2 Likes
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    No sql databases are highly scalable and much faster to use and this makes them a very attractive option for databases that are intaking tots of data. compared to SQL databases their shortfalls come from the fact that they don’t organize data in relation to each other.
  2. Do you have to defined a strict structure for your data in NoSQL?
    Data in a nosql database does not have a clearly defined structure.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    the trade off is beneficial because it allows for different use cases. This means that each type of database has many unique benefits and some are designed to intake lots of data and some are designed to intake data and organize it.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    It would be more beneficial to use an SQL database that can help organize your data
1 Like

well said *thumbs up *

  1. NoSQL is non-relational and easier to scale.It can handle Large data and updates and inserts it faster.
    2)No
    3)NoSQL is less to non- structured thus less Functionality for high performance.
    4)Not a good idea. NoSQL is non-relational.
2 Likes
  1. There’s no need to define the schema and set the data types of fields before inserting data. NoSQL is also very scalable and faster to perform than the usual operations performed on databases. NoSQL is best used when handling a vast amount of data.

  2. As opposed to relational databases, there is no need to define a strict structure for your data.

  3. Scalability is a necessary trade-off for functionality because nowadays, firms handle a vast amount of data, and it is only right that database management systems such as NoSQL cater to the majoring need for handling lots of data, as opposed to having a few extra features.

  4. NoSQL is not an appropriate database management system if the importance of relationship tracking is high.

2 Likes
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Advantages of NoSQL:

    • Non-relational
    • Easily scalable
    • Can store more data
    • Less structural setup
  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 has better scalability and performance than SQL but 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, rather use a relational database.

2 Likes
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High scalability and 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?
    This trade-off actually makes sense when large amounts of data must be quickly stored and accessed and where relations are not so important. NoSQL offers less functionality but because of that is highly 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 is better.

My Answers:

  • Easy to scale, horizontal scaling
  • Faster in most types of operations
  • Used for large amounts of data that is growing continuously
  • Stores data in JSON format, most commonly used in applications
  • No need to define a data structure before using
  1. No, you can insert and update data on the fly.

  2. No database is perfect and if you are wanting to store and retrieve large amounts of simple data without relational links, NoSQL is the better choice. NoSQL has less functionality however you can implement functionalities at the application level.

  3. No, NoSQL databases are designed not to have relationships between data.

1 Like
  1. Advantages of NoSQL: easy to scale, handles huge amount of data, stores in JSON format.
  2. You don’t need a strict structure for data in NoSQL
  3. The trade-off between scalability and functionality really needs to be accepted depending on the application you are trying to make.
  4. If your data has important relationships to keep track of, you better use an SQL rather than a NoSQL database.
1 Like
  1. Some of the advantages of NoSQL to relational databases is that they are really easy to scale and faster in operation.
  2. No
  3. NoSQL doesn’t have constraints so they are more scalable and less functional
  4. No
1 Like

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

NoSQL databases have high availability and high scalability, meaning they have better performance over SQL DB’s. They can handle huge amounts of data and they do not need to be pre-structured. They can suffer modifications in their structure on the run.

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?

Depend on the types of information and the structure you need, you would choose scalabality or functionality. If it wasn’t a problem, NoSQL DB’s would not exist in the first place beacause SQL DB’s would have cover that aspect already.

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

No, for important relationships you need to use SQL DB’s.

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

-High Scalability: The data in NoSQL databases does not need to a strict structure and sharding can be used to improve efficiency in data management and related operations, which allows to handle large amounts of data in an acceptable amount of time.

-High Availability: The auto replication feature ensures that, in case of any failure, data replicates itself to the previous state, which means that the database does not have a long downtime.

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

No – this is a big advantage of NoSQL databases because it improves scalability.

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

NoSQL databases can efficiently handle large amount of data but this high scalability comes at the cost of only providing limited insights or analyses about the relationship of the data.

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

No, in such a case relational databases are the go-to option.

1 Like
  1. noSQL = easy to scale , faster , better for storing large amounts of data
    SQL = more functionality - less performance , structured

  2. no

  3. NoSQL = semi structured / less functionality , higher performance. SQL = vice versa / structured

  4. no , use RDBMS

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    –> Scalability, availability and speed.
  2. Do you have to defined a strict structure for your data in NoSQL?
    –> I don’t. It’s flexible.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    –> It’s easier to get performance in a huge NoSQL but the price for this is the functionality, meaning that “1. You can’t have constraints in NoSQL and 2. Joins are not supported in NoSQL.
    These supports actually hinders the scalability of a database, so while using NoSQL database like MongoDB, you can implements these functionalities at the application level.”
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    –> Not really, to keep track of the relations better to use RDBMS.
1 Like
  1. Better scalability and performance and NoSQL also has better availability.

  2. No you don´t have to define a structure which is one advantage.

  3. That in order to get better scalability and performance you loose some of the function. You have to then have the functionality on the application level.

  4. Then you better go for a relational database like SQL.

1 Like
  1. ‘High scalability’ via the use of sharding for horizontal scaling; sharding is partitioning of data and placing it on multiple machines in such a way that the order of the data is preserved. Along with vertical scaling which means adding more resources to the existing machine. Vertical scaling is not that easy to implement, on the other hand horizontal scaling is easy to implement. In addition to ‘High Availability’ for example the auto replication feature in MongoDB (a NoSQL database) makes it highly available because in case of any failure data replicates itself to the previous consistent state. These are some of the advantages of NoSQL databases compared to SQL databases.
  2. You do not have to define a strict structure for your data in a NoSQL database, as it can contain either structured or semi structured data.
  3. Basically in the trade-off between scalability and functionality in NoSQL, you can’t have constraints (in relational databases constraints are rules and restrictions applied on a column or a table such that unwanted data can’t be inserted into tables), and additionally, joins (in relational databases, the SQL JOIN clause allows you to combine rows from two or more tables using a common field between them) are not supported in NoSQL. In return, these supports actually hinder the scalability of a database and in turn reduce performance. You can implements these functionalities at the application level however.
  4. If your data has important relationships that you need to keep track of ideally you need to use an SQL database not a NoSQL one.
1 Like
  1. NoSQL databases are easier to scale and have higher performance (faster) than SQL databases. NoSQL also has higher availability. It means it would perverse the last uncorrupted data if the new data has issues/corrupted.

  2. No, you do not have to define strict structures for data in NOSQL. Those structures itself can be a hindrance to a database’s ability to scale itself later on when that is necessary.

  3. It comes down to the type of data that is being preserved and whether scalability and/or relationships between your data is relevant or not that decides whether the trade-off has worth or not.

  4. It is NOT a good idea to use NoSQL since important relationships between data can only be preserved in SQL databases and NoSQL does not support such a feature.

1 Like

1)Easier to scale and performs most types of operations faster.

2)No

3)NoSQL provides scalability and performance at the cost of functionality.

4)No

1 Like