Skip to main content

Three Database Revolutions

There are three database revolutions that happened so far.  
  • The first revolution was driven by the emergence of the electronic computer.
  • The second revolution by the emergence of the relational database.
  • The third revolution has resulted in an explosion of non-relational database alternatives driven by the demands of modern applications that require global scope and continuous availability.
Lets have a look on these three waves of database technologies and discuss the market and technology forces leading to today’s next generation databases.

1950-1972 (Pre - Relational)
  • 1951 - Magnetic Tape
  • 1952 - Magnetic Disk
  • 1961 - ISAM
  • 1965 - Hierarchical Model
  • 1968 - IMS
  • 1969 - Network Model
  • 1971 - IDMS
1972 - 2005 (Relational)
  • 1970 - Codd's Paper
  • 1974 - System R
  • 1978 - Oracle
  • 1980 - Commercial Ingres
  • 1981 - Informix
  • 1984 - DB2
  • 1987 - Sybase
  • 1989 - Postgres
  • 1989 - SQL Server
  • 1995 - MySQL
2005 - 2015 ( The Next Generation) 
  • 2003 - MarkLogic
  • 2004 - MapReduce
  • 2005 - Hadoop
  • 2005 - Vertica
  • 2007 - Dynamo
  • 2007 - Neo4J
  • 2008 - Cassandra
  • 2008 - HBase
  • 2008 - NuoDB
  • 2009 - MongoDB
  • 2010 - VoltDB
  • 2010 - Hana
  • 2011 - Riak
  • 2012 - Aerospike
  • 2014 - Spile Machine
In the 20 years following the widespread adoption of electronic computers, a range of increasingly sophisticated database systems emerged.emerged. Shortly after the definition of the relational model in 1970, almost every significant database system shared a common architecture. The three pillars of this architecture were the relational model, ACID transactions, and the SQL language.

However, starting around 2008, an explosion of new database systems occurred, and none of these
adhered to the traditional relational implementations. Few of the main reasons which led to the new generation of databases is because of 3 V's.
  • Volume - High Volume of Data. Ex: MB, GB, TB, Petabytes of data. 
  • Velocity - High Velocity of Data. Ex: Batch, Periodic, Near Real Time, Real Time
  • Variety - More Variety of Data. Ex: Database, Web, Photo, Audio, Video, Unstructured
In the next blog posts we will go through few of the popular Next Generation Databases, their overall architectures  and use cases where they will be used.



Labels:

Comments

Post a Comment

Popular posts from this blog

How MongoDB survives From SQL or Query Injection

As We know SQL injection  is one of the most famous way people try to hack the SQL based applications.I came to know about interesting thing how  MongoDB  survives from this SQL injection while reading the mongodb docs. For SQL based applications most of the drivers support accessing SQL data using query as String which makes the access vulnerable. For Example in Java we use to get the data from SQL as follows, String query = "SELECT ZipCode,State FROM zipcodes WHERE City = '+city+' AND State = '+state+'"; connection = DriverManager.getConnection(jdbcurl, username, password); Statement stmt = connection.createStatement(); ResultSet rs = stmt.executeQuery(query); In case of MongoDB there is no vulnerability because all the drivers creates a BSON object for the given Query instead of calling the DB as a string itself. For MongoDb in Java QueryBuilder is used to build Queries for accesing MongoDb Data, DBObject query = QueryBu...
2 comments
Read more

GraphDatabase - The future for Facebook Recommendations

On what Basis are you getting Recommendations from Facebook??How your data is stored Internally in Social Network Sites ?? Have you ever thought how your information is stored by facebook in database?? Do you think its SQL that facebook is using for storing your data ?? If you think so ,then you are wrong.Its NoSQL GraphDatabase called 'Cassandra' what facebook uses to store your data.I know after reading this you will get lot of questions in your mind. 'What is Graph database??  How it looks like?? How it can be useful for Facebook Recommendations?? Where else it can be used??'.Let me explain each one in detail. What is Graph database?? I think Wikipedia gives the best answer for this question.So i think i can just add a link to wikipedia for the introduction of graphDatabase. Here you go..!! How it looks like?? I thing you got a basic idea about graph database after seeing Wikipedia page.Here i am showing sample example of a small Social Net...
Post a Comment
Read more