Question1) Compare between Relational database and NoSQL database.

Relational Database :

RDBMS stands for Relational Database Management Systems. It is most famous database. In it, data is keep within the shape of row this is inside the form of tuple. It comprise numbers of desk and records may be without problems accessed because records is shop within the table. This Model changed into proposed via E.F. Codd.

NoSQL :

NoSQL Database stands for a non-SQL database. NoSQL database doesn't use desk to keep the information like relational database. It is used for storing and fetching the records in database and typically used to store the massive quantity of facts. It supports query language and gives better performance.

Data Models and Schema

NoSQL databases function dynamic schema, and assist you to use what's known as "unstructured facts." This way you may build your software without having to first outline the schema. In a relational database, you are required to define your schema earlier than adding facts to the database. Not needing a predefined schema makes NoSQL databases a whole lot less difficult to update as information and requirements trade. Changing the schema shape in a relational database may be extremely highly-priced, time-consuming, and frequently contain downtime or carrier interruptions.

Data Structure

Relational databases are table-based totally. NoSQL databases may be document based totally, graph databases, key-price pairs, or wide-column stores. Relational databases had been constructed throughout a time that records changed into in the main dependent and actually defined by using their relationships. Today, we understand that records nowadays is much greater complicated. NoSQL databases are designed to deal with the greater complex, unstructured records, (along with texts, social media posts, images, movies, email) which an increasing number of make up a whole lot of the facts that exists these days.

Scaling

Relational databases are vertically scalable however commonly high priced. Since they require a single server to host the entire database, with the intention to scale, you need to shop for a bigger, greater high-priced server. Scaling a NoSQL database is a lot cheaper, as compared to a relational database, because you could upload capability by using scaling horizontally over reasonably-priced, commodity servers.

Development Model

NoSQL databases tend to be more a part of the open-supply network. Relational databases are typically closed source with licensing charges baked into using their software.

NoSQL tends to be a higher alternative for current applications which have more complicated, continuously converting information units, requiring a bendy data model that doesn't want to be right now defined. Most developers or organizations that opt for NoSQL databases, are attracted to the agile features that permit them to visit market quicker, make updates quicker. Unlike traditional, SQL based, relational databases, NoSQL databases can store and procedure facts in real-time.

While SQL databases do nonetheless have some specific use cases, NoSQL databases have many features that SQL databases are not able to managing with out outstanding charges, and critical sacrifices of pace, agility, etc.

SQL databases are called relational databases, and feature a table-primarily based statistics structure, with a strict, predefined schema required. NoSQL databases, or non-relational databases, may be record based, graph databases, key-value pairs, or huge-column stores. NoSQL databases don't require any predefined schema, permitting you to paintings more freely with "unstructured data." Relational databases are vertically scalable, however typically more highly-priced, whereas the horizontal scaling nature of NoSQL databases is more cost-efficient.

Comparison between  Relational database and NoSQL :

RELATIONAL DATABASE

• It is used to deal with facts coming in low speed.
• It gives most effective read scalablity.
• It manages dependent facts.
• Data arrives from one or few locations.
• It supports complicated transactions.
• It has single factor of failure.
• It handles information in much less extent.
• Transactions written in a single region.
• Deployed in vertical fashion.

NOSQL

• It is used to address facts coming in high velocity.
• It offers both study and write scalablity.
• It manages all type of records.
• Data arrives from many locations.
• It supports simple transactions.
• No unmarried factor of failure.
• It handles facts in excessive quantity.
• Transactions written in lots of locations.
• Deployed in Horizontal fashion.