In this tutorial of TestingLPoint, we will discuss on the History of Mongo DB and how it is created from the traditional method which is known as Flat file system.
Back in time before 1970’s we used to have Flat File system. Data and Documents are stored in the flat file in Flat File system. The problem was that each company had their own implementation of flat files. So there are no standards and lots of energy and efforts were spent in programming how to write data back to the files, how to retrieve data from files as there are no standard way of storing the data.
Every application has separate private files whose data is shared outside of its application. A report may require the data from separate file is different system which are incompatible with each other.
Another problem of Flat File system is applications are developed independently in file processing systems leading to unplanned duplicate files.
As a result it requires additional spaced in storage. If you want to change anything in a file, you need to update the same in each of duplicate file.
If we will continue with updating each file individually or manually, you may lost data integrity. Same data item may have different name in each files or vice versa.
To avoid these problem of Flat File system In 1969 Edgar F. Codd gave a Relational Theory based on that few relational database were created and these databases are answered the problem having no standard in the way the data is stored. So now there uses a standard way for storing data and standard way of querying the data.
Advantages of Relational Database
Some advantage of Relational database over Flat File system is:
- Data can be easily accessed.
- Data can be shared.
- Standard can be enforced.
- Data modeling can be flexibility.
- Data storage and redundancy can be reduced.
- Security restriction can be applied.
- Data inconsistency can be avoided.
- Data integrity can be maintained.
- Physical storage and logical data design can be maintained separately.
- Structured Query Language is easy to understand to implement in application.
So, everything was good, life was perfect, Relational database answered the problem created by the Flat File system until the data become too big. Relational database is incapable of handling the Big Data and that is by the virtue of their design, there is not Horizontally Scalable. To avoid these problems NoSQL answered the solution.
Relational Database
Below diagram is signifies the how Relational data base which was created from Flat file system.
NoSQL Database
Below diagram is signifies the how NoSQL database was created from Relational Database which was revolved from the Flat file system.
Summary:
- Data and Documents are stored in the flat file in Flat File system. The problem was that each company had their own implementation of flat files.
- So there are no standards and lots of energy and efforts were spent in programming how to write data back to the files, how to retrieve data from files as there are no standard way of storing the data.
- To avoid these problem of Flat File system In 1969 Edgar F. Codd gave a Relational Theory based on that few relational database were created.
- Relational database answered the problem created by the Flat File system until the data become too big.
- Relational database is incapable of handling the Big Data and that is by the virtue of their design, there is not Horizontally Scalable. To avoid these problems NoSQL answered the solution.
In next tutorial, we will discuss about some Introduction to MongoDB