It is no secret that the development of virtually any automated system begins with defining the format of input and output data. Data can differ significantly in its structure and organization. Some may have multiple relationships, others are simply arrays of simple data types.
We are primarily interested in two approaches to storage and manipulation of data: SQL and NoSQL.
SQL (Structured Query Language) is a structured query language used to create, modify and manage data in relational databases based on the relational data model. I think to dwell on the consideration of the same name approach is not necessary, because it is the first thing that anyone encounters when studying databases.
NoSQL (not only SQL, not only SQL) – a number of approaches aimed at implementing database models that have significant differences from the means of SQL, typical for traditional relational databases.
The term NoSQL was coined by Eric Evans when Joan Oskarson of Last.fm wanted to organize an event to discuss open source distributed databases.
The concept of NoSQL is not a complete negation of the SQL language and the relational model. NoSQL is an important and useful but not universal tool. One of the problems with classical relational databases is the difficulty in dealing with very large data volumes and in heavily loaded systems. The main goal of NoSQL is to extend database capabilities where SQL is not flexible enough, does not provide the necessary performance, and not to displace it where it meets the requirements of a particular task.
In July 2011, the company Couchbase, developer of CouchDB, Memcached and Membase, announced the creation of a new SQL-like query language – UnQL (Unstructured Data Query Language). This new language was created by Richard Hipp, the creator of SQLite, and Damien Katz, the founder of CouchDB. The development is in the public domain
Using the NoSQL approach is useful for storing large amounts of simple unstructured information that does not require a link to other data. An example of such information would be a multi-million dollar list of cache or image files. In doing so, we will get a significant performance gain over the relational approach.
Comments are closed