-
What are some of the advantages of NoSQL databases compared to SQL databases?
They are easier to scale, they are faster and can handle a huge amount of data. -
Do you have to defined a strict structure for your data in NoSQL?
I don’t believe so. -
What can you say about the trade-off between scalability and functionality in NoSQL?
NoSQL lacks the functionality of relationships of an SQL but makes up for the lack of function with better scalability and higher performance. Key Value Store, Tabular and Document based are different NoSQL type which target specific needs. -
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
Probably not.
- What are some of the advantages of NoSQL databases compared to SQL databases? fast, easy to scale and better for large amounts of data.
- Do you have to defined a strict structure for your data in NoSQL? No, you can build on the fly.
- What can you say about the trade-off between scalability and functionality in NoSQL? you give up functionality, like joins and constraints, for faster data retrieval and scalability.
- If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? no, you are better off with SQL
- More scalable and faster.
- No.
- You can’t have constraints in NoSQL. Also the data doesnt need to be well defined, however, in RDBMS it does need to be well defined.
- No
1:Advantage of No SQL they overcome the limitations of relational databases.
2:No in NoSQL you can insert, update data as you go.
3:The trade-off in NoSQL comes if you have huge amounts of data ,and don’t need to relate data with other structured data compared to a rational database.
4:If your data has important relationships amongst itself then ,NoSQL use is not a good idea, since it’s strong point is not relationship structures.
- the advantages of NoSQL are the high scalability and high availability
- no, the data is not structured and is changing over time
- when you need functionality in data, you get less performance and NoSQL isn’t appropriate for this purpose, in another hand if you want data to be easy to scale, NoSQL is the good choice.
- no, because NoSQL isn’t a Relational database. A better choice would be RDBMS.
1.What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL can easily scale and you can update and insert data on the fly. If dealing with huge amounts of data the best choice.
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?
You can’t have constraints and joins in NoSQL database.
4.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?
They are easily scalable & therefore good for huge amounts of data at a low cost.
2. Do you have to defined a strict structure for your data in NoSQL?
No, but you need a defined structure for SQL.
3. What can you say about the trade-off between scalability and functionality in NoSQL?
It really depends on the goal somebody has & the structure of the Database. If the Database is well structured and therefore has a higher functionality, there will be less performance (RDBMS should be used). Therefore, if the Database is not so much structured (less functionality) with a large Volume, NoSQL will bring the Scalibility & Performance.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No! You should consider to use a relational Database like SQL (easy relations) or Graph database (more linked relations).
- High scalability and high avaiblility
- No
- Basically, it will be better to use a NoSQL database if you need to keep track of a lot of data and the realashionship is not that important on what you need to do.
- No
Reading Assignment: NoSQL Introduction
-
What are some of the advantages of NoSQL databases compared to SQL databases?
It’s scalable and has faster performance in most types of operations. -
Do you have to defined a strict structure for your data in NoSQL?
No. It can be structured “on the fly” -
What can you say about the trade-off between scalability and functionality in NoSQL?
NoSQL has less functionality where it doen’t support constraints and joins.
It will allow NoSQL to have higher performance and scalability instead. -
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 database.
-
What are some of the advantages of NoSQL databases compared to SQL databases?
NoSQL databases were created to overcome the limitations of relational databases. One such example is RDMD requiring defining structure and schema of data first before processing the data. No SQL databases are also;
Easily scalable, faster and secure. -
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?
Reduced functionality in NoSQL however scalability is enhanced which allows for higher throughput. Functionality can be address at the application level. -
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No
- Faster, easy to scale, best for huge amount of data process.
- No.
- It is more scalable but less functional than RDMS. When you want to store and retrieve huge amount of data and constraints and joins support is not required at database level then NoSQL is your choice.
- It is better to use SQL.
What are some of the advantages of NoSQL databases compared to SQL databases?
Easy to scale.
High scalability.
High availability.
Faster.
Good for dealing with large amounts of data.
Do you have to define a strict structure for your data in NoSQL?
This is not necessary with NoSQL
What can you say about the trade-off between scalability and functionality in NoSQL?
Functionality reduces performance, so a trade-off has to be made between the two, or that greater structure can be implemented at the application stage.
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No. Relationships between data requires high functionality, so NoSQL would be far less optimal for this requirement.
1. What are some of the advantages of NoSQL databases compared to SQL databases?
- fast
- horizontal scalable
- good for handling mass data
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 data bases doesn’t have constraints and doesn’t support joins so they are more scalability and less functional.
4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No
-
Using NoSQL databases, you can enter and modify data on the go, while using SQL requires you to predefine the tables, data types and etc before you actually insert the data. NoSQL databases are also easier to scale, operate much quicker and are the best bet if we plan to have large amounts of data.
-
No, as mentioned above, you can enter and modify your data at any given time while using the NoSQL database.
-
It all just depends on the type of database you need. NoSQL trades off functionality for scalability and performance, being able to handle large amounts of data in a quick and efficient way, SQL has more functionality and handles relationships much much better.
-
Not really, this isn’t what NoSQL is good at. You would be better off using SQL as that is it’s ‘‘specialty’’. NoSQL would be if you need to store large amounts of data that are not related to each other in a complicated way (for example a thermometer or a clock).
-
What are some of the advantages of NoSQL databases compared to SQL databases?
The data could be variable, changing, or modified on the go for NoSQL while SQL database must have been previously strictly defined and cannot change after the fact. -
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?
Scalability and functionality in NoSQL are great but since its relatively less developed (more new) it has not been optimized to the extent that relational databases have so there would be an issue of efficient you could run into -
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No. For data that had important relationships to keep track of you should use SQL since the NoSQL data could be altered and relationships might be broken or severed
-
Its high scalability and its high availability.
-
No.
-
One can use NoSQL databases for huge amounts of data when the relationship between the stored data is not important and when constraints and joins support is not required at the database level as NoSQL databases can’t have constraints and they do not support joins.
-
No.
It would be way better to use a SQL database as SQL databases are designed to be used for data with relationships between the given data and NoSQL databases are not.
- Quicker operations, more scalability, JSON format allows for more compatibility with applications
- No
- There is less functionality but more scalability in NoSQL. In NoSQL, you cannot perform operations like joins and constraints.
- Nope, use SQL
- they can overcome the limitations of relational databases.One of the 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.
- no
3.NoSQL can scale itself handle huge amount of data through horizontal scaling fitting - no
-
What are some of the advantages of NoSQL databases compared to SQL databases?
The advantages are a much greater storage capacity and retrieve speed. -
Do you have to defined a strict structure for your data in NoSQL?
No, since functionality is low in the database structure. -
What can you say about the trade-off between scalability and functionality in NoSQL?
That noSQL maximises scalability but compromises complexity in the structure of the relations. -
If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
No, since it is designed for big data. In that case SQL management systems are advised.
- NoSQL doesnt need a structure, by increasing performance not using ACID and JSON format is compatible with alot of current features
- no
- you only have high availability when using sharding
- no