13:20 Aug 23, 2020 |
English language (monolingual) [PRO] Tech/Engineering - IT (Information Technology) | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Steve Wang China Local time: 07:43 | ||||||
Grading comment
|
SUMMARY OF ALL EXPLANATIONS PROVIDED | ||||
---|---|---|---|---|
5 | non-SQL data |
| ||
4 +1 | NoSQL |
|
Summary of reference entries provided | |||
---|---|---|---|
|
Discussion entries: 3 | |
---|---|
nosql data non-SQL data Explanation: A NoSQL (originally referring to "non-SQL" or "non-relational") database provides a mechanism for storage and retrieval of data that is modeled in means other ... -------------------------------------------------- Note added at 15 hrs (2020-08-24 05:01:43 GMT) -------------------------------------------------- What is NoSQL? NoSQL is a non-relational DMS, that does not require a fixed schema, avoids joins, and is easy to scale. NoSQL database is ... Introduction to NoSQL - GeeksforGeekswww.geeksforgeeks.org › introduct... Traducir esta página 5 sept. 2019 - A NoSQL originally referring to non SQL or non relational is a database that provides a mechanism for storage and retrieval of data. |
| ||||||||||||||||||||||||
18 hrs confidence: peer agreement (net): +1
|
3 days 4 hrs |
Reference Reference information: I think I might need to detail the project you guys are working on to give an accurate answer. However, there are some points you can keep in mind when deciding between relational (almost the same as saying SQL) and non-relational (almost the same as saying NoSQL) data management systems. Why do you want to go NoSQL ? is it only because of some modern, cool technologies like MongoDB, Firestore or is it because the current system using a relational database is failing at something. How big is your project and who is going to use it? If it’s small-sized project for a start-up then you can easily use NoSQL. But if the project is for a big agency like a Bank, or a big company eventually you’d need to use some transactions or have some complex relations between your data and these two are easily achievable with a relational database. How much data you have and do you picture any specific relationship between your data point in the future? If it’s very very large amount of data that for retrieving information you would have to spend so much time then NoSQL might be a good option. Is your binary data going to be all in JSON ? or it’s truly binary? Does your project plans on going to be serverless sometime in the future? if you can answer these yourself and find them out the decision could be more clear. Good Luck :call_me_hand: |
| |
Login to enter a peer comment (or grade) |
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.