SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#442

So far i have not found any use for NoSQL DBs. I have no idea why MongoDB or Casandra is so popular. It’s great that it uses JSON, but don’t need a huge DB for that. A flat file will do. People do use it but I have no idea for what. i’ll take your word on it but still need to see at least one practical use for a DB that charges bunch of money based on the amount of memory used. That’s a marketing win and i am happy for Mongo to be able to pull that off.

For my work I only use RDBMS. really could not care less about this particular topic. Sorry guys :slight_smile:

1 Like
#443
  1. Speed, scalability, auto replication;
  2. No.
  3. Scalability is worthwhile when large amounts of data need to be stored and the relations between that data (functionality) is not relevant;
  4. No.
1 Like
#444

While much of the data we store as humans is highly relational, especially in business applications, when huge amounts of data that isn’t highly relational need to be stored, Database structures like NOSQL can have some serious advantages. For example, the structure in a NoSQL DB doesn’t need to be structured beforehand, which can save a lot of time in conception, construction and implementation. Also the NoSQL DB is constantly changing over time, making adjustments in the DB autonomous. on the other hand, it could be very time consuming if you need to change things within a purely SQL DB. NoSQL databases are highly scalable, due to horizontal construction and a technique called sharding. More machines can be added to the network to increase computing power and storage capabilities. No SQL databases are also generally much faster in retrieving data. Finally, NoSQL databases uses the JSON format for storage, which is highly compatible in the business and tech world to other software and machines. While noSQL is highly scalable, there is some functionality lost in a tradeoff. Primarily, the lack of JOIN function and the inability to create constraints. Also something to consider is the lack of atomicity. Because of the sharding, all processes do not transpire at the same time on the DB. While NoSQL is a logical choice for huge amounts of Data, if your data is highly relational, noSQL would not be the best choice, as it is difficult to organize the information into relationships in a manner for fast retrieval

2 Likes
#445

High scalability by using sharing as a horizontal scaling and high availability with the auto replication feature.

Required for SQL dBs, not for NoSQL dBs.
3.
In order to bring efficiency on fast operations working with a high amount of data, scaling is more important therefore NoSQL dBs, could meet these needs. In this case, functionalities are better implemented on the application layer, rather than on dB.
4.
Relational Database Management Systems like SQL makes more sense in this case.

1 Like
#446

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

    It has a low cost, it's  more fast and easy to scale.

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

           Nope.

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

    It provides more functions, but not so good performance, it's limited too.

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

    No, I'd prefer more RDBMS.
1 Like
#447

SQL and Relationship Databases - Reading

  1. NoSQL advantages over SQL databases are:
  • easy to scale
  • faster in operation
  • high availability like open-source
  • store on Json Format
  • flexible and ease of use
  • lower cost

  1. No, you don’t have to define a strict structure for your data in NoSQL because you cannot have constraints or joins that are supported as in SQL.

  2. Trade-off between scalability and functionality in NoSQL is that if you need to store data as it grows you choose NoSQL scalability aspect of the database. Functionality, on the other hand, hinders the scalability aspect of the database. If you are using say MongoB, this functionality can be implemented on the application level.

  3. If you need to keep track of important relationship in a data, DO NOT USE NoSQL because the relationship aspect is not important in the NoSQL database. You will have to use SQL database which is very good for integrity of important relationships.

1 Like
#448

  1. NoSQL provides scalability and high availability.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No. Constraints and Joins support is not required at the database level.

    1. If you need to scale, change data types and need flexibility over time and don’t need to relate data with other data or need to structure data, then it could be worth trading scale and efficiency of NoSQL over the functionality of a relational database.
    1. No, it would be better to use a RDMS.
1 Like
#449

  1. The advantages of NoSQL over SQL are high scalability and high availability.

  2. In NoSQL it is not necessary to define a strict structure for your data.

  3. NoSQL provides high performance and scalability at the cost of functionality. There are no constraints in NoSQL and Joins are not supported either.

  4. If your data has important relationships that you need to keep track of, NoSQL is not the best choice.

1 Like
#450

1.) What are some of the advantages of NoSQL databases compared to SQL databases?
The main advantages are high scalability and high availability.

2.) Do you have to defined a strict structure for your data in NoSQL?
No! NoSQL databases are different than relational databases like MySQL.

3.) What can you say about the trade-off between scalability and functionality in NoSQL?
NoSQL: Structured or semi structured data, less functionality and high performance.

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 has important relationships that you need to keep track of you have to use relational databases like MySQL.

1 Like
#451

  1. NoSQL databases have high scalability and can handle huge amounts of data due to using sharding for horizontal scaling. Data is also highly available in a NoSQL database because in the event of a failure, the data replicates itself to its previous state. NoSQL databases also perform most types of operations faster than other databases.

  2. You do not need to define a strict structure when using a NoSQL database because they store data in the form of JSON objects.

  3. When using a NoSQL database, you are trading scalability and performance for functionality. Reduced functionality in this case refers to the fact that you can’t have constraints or joins in a NoSQL database.

  4. No, this is not a good idea. It would be better to use a relational database in this case.

2 Likes
#452
  1. High scalability and high availability
  2. No
  3. NoSQL works better for large amounts of data and it is cost time effective as long as data security is not a priority
  4. No
1 Like
#453
  1. You can insert and update data on the fly. It is easy to scale and faster.
  2. No, you haven’t.
  3. Scalability is high and functionality is less.
  4. No, you should rather use RDBMS.
1 Like
#454
  1. In NO SQL database you can insert and update data easily.
  2. No
  3. In noSQL DB there is less functionality and more scalability
  4. No if the important data are related you need to use an SQL DB.
1 Like
#455

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?
NoSQL is more scalable but has less functionality on de database level.

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

1 Like
#456

1,
faster,can store data in the ‘air’, bigger capability
2,
no, you only have to do that in relational databases
3,
higher scalability, less functionality
4,
No, NoSQL has many positive uses but keeping up relationship between data is not one of them. Go for SQL database then

2 Likes
#457
  1. NoSQL databases compared to SQL databases offer several advantages; these include: a scalability to grow the BD to contain huge amounts of data (easily horizontally scalable), high availability , stores its data is JSON (increased compatibility with modern applications)
  2. NoSQL does not require a struct structure definition prior to inputting data, in fact, no structure definition is required
  3. The trade-off between scalability and functionality in NoSQL is clear, scalability is almost unlimited and its performance is usually better than SQL DBs, whereas functionality does take a hit where constrains and joins are not supported but these last 2 can be handled at the application level.
  4. If the data has important relationships that need to be kept track of, is it a good idea to use SQL? NoSQL does not perform well in this area.
1 Like
#458
  1. Advantages of
  • NoSQL databases
    efficience
    Scalability

management of:
huge amount of data to store and retrieve,
continuously growing data
evolving, changing over time, and not structured data
only when contraints and joins are not required at database level

  • SQL databases
    most commun
    relational data
    secure because of atomic transaction
    structure and define data by the fundation

  1. No strict structure needed for your data in NoSQL

  2. scalability and functionality in NoSQL
    more performance and functionalities as long as not required at DB level - less funct. - they can be implemented at the application level.

  3. When important relationships are needed to get kept track of, SQL is king and not NoSQL.

2 Likes
#459

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    NoSQL is easier to scale and does not have a defined schema compared to SQL which gives an advantage to the performance and upgradability of NoSQL databases.

  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 trades off functionality to gain performance and scalability which allows NoSQL databases to handle huge and growing amounts of data. NoSQL is does not have support for constraints or joins at the database level though but these can be implemented 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?
    No, if relationships are important in the database it would be better to use a RDMS.

1 Like
#460

1 better scalability and Performance. And more flexible
2 No you can change the structure without to many consequences
3 The more scalability the less functionality
4 No

1 Like
#461

SQL and Relational Databases:

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    The main advantages of NoSQL are high scalability and high availability.
    Since there are no Joins on NoSQL it can process information a lot faster and it is very easy to expand horizontally. As the data volume increases NoSQL scale itself to handle that data in efficient manner.
    High availability of data is an important feature. In case of MongoDB - it makes it highly available and in case of failure, data replicates itself to the previous consistent state.

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, we do not have to do that - we can update and add data without setting up defined structure, scheme (relationships and joins are not required on data base level).

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    Scalability of NoSQL is a strength of that type of data base but functionality is sort of weakness. But in right application scalability and speed of processing could be more beneficial than advanced relationship processing.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    If relationships are a priority, I would suggest using RDBMS (Relational Database Management Systems).

G.

1 Like