SQL and Relational Databases - Reading Assignment

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    scalability, high performance, speed

  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?
    having a huge amount of data with no relations

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, altough you can implement relations in application layer

  1. One advantage is High scalability, like using sharding (more machines to handle the data) in Horizontal scaling, it takes the strain off of one machine to handle all the data…I think.

Data does not need to be as structured, for example you can just have an ‘object’ that contains a key and a value…very short and sweet. As in:

{
“_id”: “02654”
}

Where “_id” is the key
And “02654” is the value assigned to that key
the colen simply separates the key from the value in this dataset

So the advantage is you can have multiple objects, each structured differently, but be able to search all objects against for example one particular key.

  1. As explained in my answer to 1 above, no, there is much more flexibility, however JSON is common.

  2. Well, you get the advantage of scalability, but if you understand the role joins and ability to use constrains are, well, you don’t get those…

  3. Apparently no, but I’m not sure why at this point.

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Scaleability and using JSON rather then formatting all your data and relationships.

  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?
    Sharding allows for horizontal scaling. Things like data comparison happen outside the database on an application layer rather than in the database like SQL.

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

It is a bad idea to use No SQL in this situation and much better to use an SQL database.

  • High scalability. Use horizontal scaling through sharding, much easier to handle large amount of data and doesn’t slow down when scaled.
  • High availability. In case of database failure it replicates itself to the previous consistent state.
  • Flexibility. No need to worry a defined structure, table, schema during setup. Insert and update data on the fly.
  1. No

  2. NoSQL has higher scalability but less functionality. If you need a database that doesnt require much functionality and foresee rapid scaling, then it is w worthy trade off.

  3. No. SQL is a better solution due to the importance of relationships.

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

  2. Do you have to defined a strict structure for your data in NoSQL?
    Not really

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    In order to have scalability, functions such as Joins or constraints cannot be present and that is why NoSQL allows for flexibility in scalability.

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

1 Like
  1. Can hold large amount of data and can be structured horizontally while there is no need for a perfect detailed structure within the DB

  2. No

  3. You trade loosing precise and detailed functionality by having easy scalabilty and availabilty using NoSql

  4. No - you are batter with a SQL database (a relational database)

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • You can insert, update data on the fly

  • Really easy to scale

  • Much faster in most types of operations that we perform on database

  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?

  • Sharding for horizontal scaling

  • Horizontal scaling means adding more machines to handle the data.

  • Joins are not supported in NoSQL

  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, you would want to us SQL, RDBMS.
  • What are some of the advantages of NoSQL databases compared to SQL databases?
    1.high scalibility: when need higher performance, just add machine for horizontal scaling.
    2.high avalibility: MongoDB provide auto replication feature.when something wrong, we can easily back to previous consistant sate.

  • Do you have to defined a strict structure for your data in NoSQL?
    NoSQL use JSON structure ,we don’t need to define a strict sturcure like relational database.

  • What can you say about the trade-off between scalability and functionality in NoSQL?
    If we need deal with huge data ,and constraint and join support not need in dabasebase level,then NoSQL is a better choice .

  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    In that case , maybe I will consider SQL Dabase is a better choice .

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    They are very scalable. In addition, it also has high availability.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, you do not. That is an advantage of NoSQL.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    There are some functionality limits in NoSQL. For example, you can’t have ‘joins’ or ‘constraints’ in NoSQL.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, it’s not. You’d want to use a SQL database in that case.

1 Like

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

NoSQL include being able to handle:

Large volumes of structured, semi-structured, and unstructured data

Agile sprints, quick iteration, and frequent code pushes

Object-oriented programming that is easy to use and flexible

Efficient, scale-out architecture (scalability) instead of expensive, monolithic architecture

High Availability: Auto replication feature in MongoDB makes it highly available because in case of any failure data replicates itself to the previous consistent state.

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

No, it can be structured or semi structured data

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

RDBMS It is a structured data that provides more functionality but gives less performance .
NoSQL: Structured or semi structured data, less functionality and high performance .

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

It would not be a good idea, because NoSQL will not be able to maintain those relationships needed to track your data.

1 Like
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Highly Scalable,
    No need to define the structure in DB level
    Works with JSON format
    Suitable for huge amounts of Data
  2. Do you have to defined a strict structure for your data in NoSQL?
    It will not be defined in Database level.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    NoSQL is highly scalable but less functional since the information is thrown without a structure which needs to be worked on in application stage.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    SQL databases are better choice for relation based DBs
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  1. You can insert and update data on the fly (no need to create tables, define schema, etc. in advance)
  2. Easy to scale
  3. Some databases have an automatic replication feature in case of failure
  4. It is faster in situations where relationships are not required
  5. Best for huge amounts of data
  6. NoSQL stores its data in JSON format, which is compatible with most of today’s applications
  1. Do you have to defined a strict structure for your data in NoSQL?
    No, that is one of the benefits

  2. What can you say about the trade-off between scalability and functionality in NoSQL?
    If the nature of the data is non-relational, or a huge amount of data needs to be stored, or the data does not need to be restructures or changed over time, then NoSQL’s scalability benefits outweigh the lack of functionality.

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

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

Fast, scalability, less requirements to structure data, able to handle large amounts of data in clusters.

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

Null

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

The ability to do complex query’s, is traded for scalability through unstructured data which allows larger, quicker storage of data.

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

Null, NoSQL has advantages for large volumes of non-critical data; weather data, where SQL has advantages for reliability for example; financial services.

1 Like

1. What are some of the advantages of NoSQL databases compared to SQL databases?
Scalability,
High Availability,
JSON support
Doesn’t require schema design, tables etc upfront,
Can handle voluminous data
2. Do you have to defined a strict structure for your data in NoSQL?
No. That is the major advantage.
3. What can you say about the trade-off between scalability and functionality in NoSQL?
Scalability is inherent to NoSQL but provides less functionality as there is no support of ‘Constraints’ and ‘JOINS’, which can be address at application level anyway.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No. Use RDBMS.

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    • Scalability, performance, simplier, high 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?
    • Scalability and performance versus functionality
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    • No, use SQL instead
  1. What are some of the advantages of NoSQL databases compared to SQL databases? – For NoSQL Databases you do not have to structure them in advance. Its main advantage is the handling of huge amount of data. It is fast in responding and more scalable than SQL.

  2. Do you have to defined a strict structure for your data in NoSQL? - NoSQL Databases do not have to be structured in advance.

  3. What can you say about the trade-off between scalability and functionality in NoSQL? – NoSQL is more scalable, but therefore has loosing the functionality of constraining data and having relations depicted.

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

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High scalability and high 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?
    The scalability and functionality goes in different ways when we use NoSQL. if we want to increase one we trade-off part of the other
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No
  1. No need to set up the table initially, can be modified anytime , great for bid amount of data, also high scalability and high availability.
  2. No
  3. the more structure/ relation you need the less scalable the data base its and vise-versa
  4. No, for relationships use SQL or other relational databases
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Some of the advantages are that NoSQL databases are really easy to scale. They are also much faster on most operations that are performed on a database. They are much better at dealing with large amounts of data than SQL databases.
  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 we get less functionality but there is more scalabilty.
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, this would be a better scenario to use a SQL database instead.
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    Its more scalable and can process more data. You are also able to add data on a fly. Which means you can adjust your tables and you can adjust the datastructure

  2. Do you have to defined a strict structure for your data in NoSQL?
    No you can add data on the fly.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    It allways depends on your use case and then you can decide where to do the trade off. If you have alot of data coming in every day like daily measurments than you are better of with NoSQL. If you need relations than you choose SQL.

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