The Future of Database: No SQL

by Vincent S
As businesses continue to become more reliant on the integration of new communications technologies and services, it has become more difficult to ensure that all the technologies use similar platforms.  Databases are no longer only stored on in-house servers.  Many company databases are stored on a combination of in-house servers and public cloud computing servers for data storage.  With this in mind, one can see the challenge in keeping all the databases homogeneous enough in format in order to keep the rules of referential integrity.  For many years software developers have attempted to solve this problem by creating databases that do not use SQL.  In October 2011, Oracle announced the release of their own database that lacks the use of SQL.  The obvious advantage of this type of database is that it does not matter on what platform or operating system the database was created on.  Advocates of this method of database agree that large quantities of unstructured and unformatted data become much easier to deal with.
This article relates to what we have talked about in class this week in sense that it introduces a new kind of data model.  However, the no SQL model is different from anything we mentioned in class.  Using software that lacks use of SQL allows for customizable behavior that does not restrict data to a row and column format.  This concept has the additional advantage of faster processing among a string of low-end servers which can help keep costs way down.  The most obvious disadvantage is the lack of an ability to merge tables once they are complete.  This makes achieving referential integrity almost impossible once too much heterogeneous data is entered into the same database.

I find it extremely interesting that the field of CIS is so dynamic in nature.  Just as we are learning about data models in class, new software that uses a new model is being implemented in the industry.  Newcomers in the industry must always be ready to learn new methods and protocols as quickly as they are created.

Metz, Cade. (2011, October 03). Retrieved on January 15,2010 from

3 thoughts on “The Future of Database: No SQL

  • January 15, 2012 at 6:06 pm

    It pretty interesting to know that people are search for a alternate to SQL, but I don’t think it would over take SQL for a while. The security on public hosting server can be a major problem for big company that have sensitive information on their database.

  • January 15, 2012 at 7:43 pm

    Wow everything is going to “Cloud” system, I agree with Quoc a security will be problem for a major company just think like T-mobile having a cloud database, it can jeopardize customer information.

  • January 15, 2012 at 9:12 pm

    I have also read something about how some people wanting to move away from using relational database to more of a database that works with the cloud. I think there are a couple of database management softwares out there but none of those really have anything that address the current issue with security.

Comments are closed.