Not Only SQL
(NOSQL)
In this paper I will use comparisons to help distinguish what is NOSQL. We will talk about NOSQL vs SQL. Document, Graph, or Key-value and wide column Models of NOSQL. We will touch on Schema and end with a condensed comparison of SQL and NOSQL. In short, a brief overview of not only NOSQL but also its opposing and conjoining systems, and their pro’s and con’s.
To really understand these comparisons, you need to have an Idea of what JavaScript and JSON are in addition to the LAMP and MEAN stacks. The term LAMP referrers to (Linux, Apache, MySQL (SQL), PHP). The LAMP stack is a common stack of open source and free languages. This stack uses Linux as the operating system Apache as the server, MQSQL as the Database and PHP …show more content…
JSON stands for: JavaScript Serialized Object Notation. It is a minimal format for structuring data, and was created for use in JavaScript to pass around small bits of data. “JSON is the data structure of the Web. It 's a simple data format that allows programmers to store and communicate sets of values, lists, and key-value mappings across systems.” Ok so NOSQL is a database system that does not use the traditional tables columns and rows. It uses one of the outlined Data Models above. For comparison we are using Mongo DB, a popular NOSQL option, which uses the Document Model, whose format is similar to JSON, which we have now defined.
In addition to Document NOSQl databases, there are also Graph, Key-value and wide column Models. These each are a topic to wide to discuss here but we will touch briefly on each.
• Graph databases use embedded aggregates, like other NOSQL databases. Graphs are capable of manipulating large amounts of data. Graphs work by using two type of records, Nodes and Relationships, these intern have properties. The best way to visualize this is to think of an Entity relation diagram, with labeling between the entities describing the relationships.
• Wide column databases is an exception to the rows and columns rules. The data her eis stored in rows with an associated key, and they are ordered by column, however the difference here is that each row can have different columns. Theses columns can be made into super columns which are …show more content…
These models do vary between different kinds Berkely Db and Couchbase are a few to mention.
Aside from the aforementioned items above, these databases continue to differ from one another. RBDMS like MYSQL is great for a variety of different applications. It is proven to be a viable database structure. The problems start with RBDMS when there are errors in the design of the database, or growth into larger data occurs. This requires you to continually upgrade the server space to accommodate the growing data. This does not mean, however, that every database should or could be a NOSQL type. While NOSQL has the ability to perform data calls at a very fast speed, very strong write speeds on large amounts of data, it offers only a few capabilities to preform ad-hoc queries, it has may different Document types and is skill heavy.
The condensed take away is this. “The right tool for the right job”- . There are many attributes that each type of database, SQL vs NOSQL, has. RBDMS has been the standard for many years (even replaced NOSQL at one point) and will not be going away. Not every application can use NOSQL to its potential, again noting on the skill requirement referencing load balancing and cluster
(NOSQL)
In this paper I will use comparisons to help distinguish what is NOSQL. We will talk about NOSQL vs SQL. Document, Graph, or Key-value and wide column Models of NOSQL. We will touch on Schema and end with a condensed comparison of SQL and NOSQL. In short, a brief overview of not only NOSQL but also its opposing and conjoining systems, and their pro’s and con’s.
To really understand these comparisons, you need to have an Idea of what JavaScript and JSON are in addition to the LAMP and MEAN stacks. The term LAMP referrers to (Linux, Apache, MySQL (SQL), PHP). The LAMP stack is a common stack of open source and free languages. This stack uses Linux as the operating system Apache as the server, MQSQL as the Database and PHP …show more content…
JSON stands for: JavaScript Serialized Object Notation. It is a minimal format for structuring data, and was created for use in JavaScript to pass around small bits of data. “JSON is the data structure of the Web. It 's a simple data format that allows programmers to store and communicate sets of values, lists, and key-value mappings across systems.” Ok so NOSQL is a database system that does not use the traditional tables columns and rows. It uses one of the outlined Data Models above. For comparison we are using Mongo DB, a popular NOSQL option, which uses the Document Model, whose format is similar to JSON, which we have now defined.
In addition to Document NOSQl databases, there are also Graph, Key-value and wide column Models. These each are a topic to wide to discuss here but we will touch briefly on each.
• Graph databases use embedded aggregates, like other NOSQL databases. Graphs are capable of manipulating large amounts of data. Graphs work by using two type of records, Nodes and Relationships, these intern have properties. The best way to visualize this is to think of an Entity relation diagram, with labeling between the entities describing the relationships.
• Wide column databases is an exception to the rows and columns rules. The data her eis stored in rows with an associated key, and they are ordered by column, however the difference here is that each row can have different columns. Theses columns can be made into super columns which are …show more content…
These models do vary between different kinds Berkely Db and Couchbase are a few to mention.
Aside from the aforementioned items above, these databases continue to differ from one another. RBDMS like MYSQL is great for a variety of different applications. It is proven to be a viable database structure. The problems start with RBDMS when there are errors in the design of the database, or growth into larger data occurs. This requires you to continually upgrade the server space to accommodate the growing data. This does not mean, however, that every database should or could be a NOSQL type. While NOSQL has the ability to perform data calls at a very fast speed, very strong write speeds on large amounts of data, it offers only a few capabilities to preform ad-hoc queries, it has may different Document types and is skill heavy.
The condensed take away is this. “The right tool for the right job”- . There are many attributes that each type of database, SQL vs NOSQL, has. RBDMS has been the standard for many years (even replaced NOSQL at one point) and will not be going away. Not every application can use NOSQL to its potential, again noting on the skill requirement referencing load balancing and cluster