SQL and Relational Databases - Reading Assignment

Blockchain Business Course
#602

1- high scalability and high availability.
2- No
3- Structured data provides more functionality . less structured data, for large volumes of data, it is better to choose NoSQL
4- No

1 Like
#603
  1. What are some of the advantages of NoSQL databases compared to SQL databases?

No SQLDatabases allow high scalability through sharding / horizontal scaling (adding more machines to handle and maintain the data). Also, No SQL enables high availability of the database through auto replication

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

No, data can be inserted or updated as required without the need for first establishing a strict structure

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

No SQL enables greater scalability because of the less rigid structure requirements, however the functionality for No SQL is reduced as a result

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

No, NoSQL is good for enabling storage and retrieval of a huge amount of data, but does not support the maintenance of strict structure and relationships among data

1 Like
#604
  1. High scalability and high availability
  2. No - you can just insert/update records on the fly
  3. The trade-off is worth it when you’re dealing with a dataset that won’t require the functionality NoSQL databases lack - e.g. large fairly simple datasets; also if required most of the extra functionality can be implemented in the application layer
  4. No
1 Like
#605

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    High Scalability and High Availability, high performance

  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?
    Less funcionality but higher scalability and performance

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

1 Like
#606
  • What are some of the advantages of NoSQL databases compared to SQL databases?
    Can have high performance and volume and very little resources are used.
  • Do you have to defined a strict structure for your data in NoSQL?
    No there is less structure which improves speed and performance
  • What can you say about the trade-off between scalability and functionality in NoSQL?
    The more scalable an application becomes in order to maintain operability it is best to have lighter functionality.
  • If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No having a relational database would be best for this type of application.
1 Like
#607
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  • Scalability,
  • Availability (after failure data returns to previous state),
  • Performance.
  1. Do you have to defined a strict structure for your data in NoSQL?
  • No. Data is stored in JSON format and can be structured or somewhat structured, or not.
  1. What can you say about the trade-off between scalability and functionality in NoSQL?
  • Data stored like this cannot be linked to other data. That could be handled by an application if needed.
  • NoSQL is useful for large amounts of data that doesn’t need many relations in between.
  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
  • No.
1 Like
#608
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
  2. Do you have to defined a strict structure for your data in NoSQL?
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?

1)High scalability and high availability. A low cost database.
2)No
3)Structured data provides more functionality than scalability, so when you would need a less structured data but a need to store large volumes of data, it is better to use NoSQL.
4)No

1 Like
#609

  1. The biggest advantages are high scalability and availability.

  2. No you don’t have to.

  3. Using NOSQL trades security over performance and scalability and high availability in case of any failure, data replicates itself to the previous consistent state.

  4. No because of posibility of delayed response, better t use RDMS.

1 Like
#610
  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    It has increased performance and scalability potential.
  2. Do you have to defined a strict structure for your data in NoSQL?
    No, you do not.
  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    They are directly proportional meaning less functionality means more performance and scalability. In order to “add” functionality you need to implement it at 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, it is not.
2 Likes
#611
    • For huge amount :mountain_snow: of data it is easy to scale
    • Faster :running_woman:t3: to get in operation to process data
  2. If constraints and joins are not needed as a structure :bento:,
    NoSQL can process unstructured :shallow_pan_of_food: data
  3. Prefer NoSQL scalability over functionality when
    a. store and retrieve huge :mountain_snow: data
    b. relationships :broken_heart: are not important
    c. data is not structured :shallow_pan_of_food: and changes :cyclone: over time
    d. no constraints and joins :symbols: are required
    e. data is growing continuously :cyclone: and scale :rocket: the database
  4. Nope NoSQL.
    (:couplekiss_man_woman: You’ll need SQL to serve robust dataprocess execution on reliability, validity, integrity of those important relationships in the database.)
1 Like
#612
  1. Scaling and high accessibility
  2. No
  3. Although NoSQL is good for high amounts of data using variable structures, it has low functionality and does not work with relationships
  4. No
1 Like
#613

  1. What are some of the advantages of NoSQL databases compared to SQL 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.
    The main advantages are 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?
    For more scalability you get less performance.

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

1 Like
#614

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    You can insert, update data on the fly / handle massive & constrant data and data revisions, easier to scale / escalate information, fast reference in certain operations. CRUD compatable. No - data can be added or revised in any sequence given the hierarchical data structure.

  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?
    Speed and accuracy / precision are the guiding criteria for the proper selection between the databases. A key factor is relationship enforcement, as it gives you the chance to run complex operations and to preserve data integrity at the cost of a slower performance and a previously-defined structure. Further, data can be updated / revised on the fly / in the moment.

SQL --> Baking & Financial Transactions require defined structure and limit fast scalability and may slow computation.

NoSQL --> Massive data surges, updates, collection & delineation of field data require scalability over the specific accuracy required in a formalized SQL data structure.

  1. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL? No - the whole purpose of NoSQL databases / were created to overcome the limitations of “Relational Databases.”

rjr
2021-03-26T04:00:00Z

2 Likes
#615

Thank you for your contribution to the forum! Your response for 3. made it clearer for me to understand what was being asked. Appreciate it!

1 Like
#616

  1. What are some of the advantages of NoSQL databases compared to SQL databases?
    You are not constrained by your intitial database design scheme, you are able to input date and update the design in real time.
    Additionally, NoSQL databases are easy to scal and work faster (in most cases).

  2. Do you have to defined a strict structure for your data in NoSQL?
    No, this database type is flexible/dynamic - able to be changed, updated and reorganized as you work or as needs change, etc.

  3. What can you say about the trade-off between scalability and functionality in NoSQL?
    More scalability generally means less functionality but there are plenty of high-data instances where this trade off is completely acceptable.

  4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
    No, a relational SQL database would be more appropriate.

2 Likes
#617

1. What are some of the advantages of NoSQL databases compared to SQL databases?
A: The 2 main advantages are:
High scalability: NoSQL databases sharding for horizontal scaling. Sharding is partitioning of data and placing it on multiple machines in a way that the order of the data is preserved. Vertical scaling (not as easy to implement as horizontal scaling) means adding more resources to the existing machine while horizontal scaling means adding more machines to handle the data. Horizontal scaling database examples: MongoDB or Cassandra. Because of this feature, NoSQL can scale itself to handle more data in efficient manner.
High Availability: Auto replication feature makes it highly available because 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?
A: No. This is not required implying that no upfront database model design is required

3. What can you say about the trade-off between scalability and functionality in NoSQL?
A: Functionality is somehow compromised in a NoSQL database as one can’t force constraints on data (which ensure consistency at a database level) and joins are not supported. These features must be supported at the application level; On the other hand, NoSQL delivers better scalability

4. If your data has important relationships that you need to keep track of, is it a good idea to use NoSQL?
A: No as only SQL DB’s provides consistency and integrity of data at the database level by enforcing ACID properties: Atomicity, Consistency, Isolation and Durability.

2 Likes
#618
  1. SQL databases you need to create the table, define schema, set the data types of fields before you can insert the actual dat. In NoSQL you can insert and update data on the fly. NoSQL database is really easy to scale and are much faster in most types of operations and are preferred for huge amounts of data.
  2. No
  3. NoSQL high scalability includes - Vertical scaling means adding more resources to the exiting machine while horizontal scaling means adding more machines to handle the data. The trade off with functionality in NoSQL - You can’t have constraints and Joins are not supported.
  4. No
1 Like
#619

  1. Faster, scalable and flexible.

  2. No.

  3. It is not atomic and therefore less secure.

  4. No.

1 Like
#620
  1. Advantages of NoSQL databases compared to SQL databases include not having to define parameters when they are set up (so more flexible); being faster to add/retrieve information (because it doesn’t have to be sorted and matched); being much easier to efficiently scale up because you can simply add storage (new machines) for horizontal scaling rather than having to add resources to your exiting, original set up (vertical scaling) - horizontal scaling is faster and cheeper; and it is easier to clone so that backup versions are always available in the case of failure (high availability).
  2. You do not have to defined a strict structure for your data in NoSQL.
  3. The trade-off between scalability and functionality in NoSQL basically break down into how much you need to be able to grow and expand the system, vs how much you need the pieces of data in the system to talk to each other (SQL is better at relations between data, and can apply constraints or joins on a database level), and how much cross verification (IE Security) is needed (SQL is better at limiting parameters, cross verifying).
  4. Data with important relationships that you need to keep track of should not use NoSQL.
2 Likes
#621

1: It is easier to scale, simpler to change and update hardware. “Horizontal scaling” to clusters. Easier to add new computers, but must be synced. Also, very high availability.
2: No.
3: You trade off functionality for scalability with NoSQL. However, for certain data sets or data streams high functionality with relations is not necessary. What is necessary is the ability to scale horizontally when data sets continue to expand and grow.
4: No, use SQL

1 Like