Loved your answers. It’s easy to understand. Great work.
Carlos Z.
Loved your answers. It’s easy to understand. Great work.
Carlos Z.
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?
NoSQL is less secure, but great for database for high scalability.
In case of any failure data replicates itself to the previous consistent state.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No.
1.What are some of the advantages of NoSQL databases compared to SQL databases?
It can deal with large data sets faster than SQL which allows scalability.
NoSQL you do not need to create complex schema.
The developer can change the data format in NoSQL.
2.Do you have to defined a strict structure for your data in NoSQL?
No. It will be contained in a JSON format.
3.What can you say about the trade-off between scalability and functionality in NoSQL?
Since the NoSQL contains data more simple than SQL, the scalability is good.
But at the same time you cannot pull out the datas with complex query.
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 better to use SQL.
The advantages for NoSQL databases are High Scalability and Availability.
No NoSQL does not need a strictly defined structure.
NoSQL gives improvements in scalability and performance at the expense or a loss in functionality.
No NoSQL is not suited to an application requiring the tracking of important relationships.
1: It is low cost, scalable and easy to restructure.
2: No
3: It is useful depending on the type and volume of data that needs storing.
4: No
What are some of the advantages of NoSQL databases compared to SQL databases?
Handle large volumes of data at high speed, easier to scale, no structure needed.
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?
The trade-off depends on your needs. If the data is relational and require atomicity then SQL DB is recommended but if the data is non relational and large volume choose NOSQL.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No, its a very bad idea
1.What are some of the advantages of NoSQL databases compared to SQL databases?
Apart from not having to create tables, define schema, set the data types of fields etc before actually inserting the data… 1)high scalability meaning really easy to scale and much faster in most types of operations and 2) high availability meaning that in case of any failure, data replicates itself to the previous consistent state.
2.Do you have to defined a strict structure for your data in NoSQL?
Nah, data can be inserted and updated on the go.
3.What can you say about the trade-off between scalability and functionality in NoSQL?
While constraints in NoSQL aren’t possible and joins aren’t supported, these supports actually hinder the scalability of a database. By using a NoSQL database, these functionalities can be implemented at an application level.
4.If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Probably not, but it depends on the data and whether it needs to be updated or not. For e.g. a bank that needs to keep track of transactions, a relational database system is preferable because it provides consistency and integrity of data by enforcing ACID properties (Atomicity, Consistency, Isolation and Durability ).
Advantages of NoSQL are high scalability and high availability, and you can insert, update data on the fly.
Strict structure does not need to be defined in NoSQL.
The trade-off between scalability and functionality is that joins and constraints are not supported thus hinders scalability.
No.
1 in nosql, just fill in the fields, and in sql you have to choose all the info you want to insert
2 in
3 nosql database is scalable
4 its better on sql
One advantage of 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. Another advantage is that NoSQL can handle much more data than a Relational database such as SQL.
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?
NoSQL databases doesn’t have constraints and doesn’t support joins. This being said NoSQL more scalability, and as a result offer less functionality.
No, when there is a need for relationships to be drawn upon then it is better to use SQL.
What are some of the advantages of NoSQL databases compared to SQL databases?
• Insert, update data on the fly.
• Easy to scale and faster than SQL.
• Handle large amounts of data. High availability and scales horizontally without losing data.
2. Do you have to defined a strict structure for your data in NoSQL?
No. Hence in the name NoSQL. Data are stored in a JSON format.
3. What can you say about the trade-off between scalability and functionality in NoSQL?
No constraints, larger data sets and doesn’t support joins. This means faster access to the data source.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No. Banking data is a good example where you should use an RDB where as something thats doing IOT or real time timestamping of temp. or heat, NoSQL is more ideal over time.
Do you have to define a strict structure for your data in NoSQL?
No you don’t.
Trade-off between scalability and functionality in NoSQL
You don’t have support for joins and constraints as price for scalabilty and performance.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Since NoSQL databases don’t guarantee atomicity of transactions and also have way less capability to represent relationships it is not a good idea at all.
Really easy to scale, much faster in most types of operations that we perform on database, no need to define structure and schema of data first before processing data, high availability and high scalability.
No.
The trade-off are the following:
-Can’t have constraints in NoSQL
-Joins are not supported in NoSQL
No.
Reading Assignment: NoSqL databases (Answers)
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
I think you misunderstood the question, are you sure that you will use NoSQL for relationship database?
If you have any more questions, please let us know so we can help you!
Carlos Z.