Various Databases – Comparison

A database is an organized collection of data. It is the collection of schemes, tables, queries, reports, views and other objects. The data is typically organized to model aspects of reality in a way that supports processes requiring information, such as modelling the availability of rooms in hotels in a way that supports finding a hotel with vacancies.

A database management system (DBMS) is a computeimagesr software application that interacts with the user, other applications, and the database itself to capture and analyze data. A general-purpose DBMS is designed to allow the definition, creation, querying, update, and administration of databases.

Choosing the right database system makes a difference. Some work on specific operating systems, while others don’t. Lets dig into some of them.

Redis (V3.0RC)

  • Written in: Credis-white
  • Main point: Blazing fast
  • License: BSD
  • Protocol: Telnet-like, binary safe
  • Disk-backed in-memory database,
  • Dataset size limited to computer RAM (but can span multiple machines’ RAM with clustering)
  • Master-slave replication, automatic failover
  • Simple values or data structures by keys

Cassandra (2.0)

    • Written in: Javacassandra_logo
    • Main point: Store huge datasets in “almost” SQL
    • License: Apache
    • Protocol: CQL3 & Thrift
    • CQL3 is very similar SQL, but with some limitations that come from the scalability (most notably: no JOINs, no aggregate functions.)
    • CQL3 is now the official interface. Don’t look at Thrift, unless you’re working on a legacy app. This way, you can live without understanding ColumnFamilies, SuperColumns, etc.

HBase (V0.92.0)

  • Written in: Java
  • Main point: Billions of rows X millions of columns
  • License: Apache
  • Protocol: HTTP/REST (also Thrift)hbase_logo
  • Modeled after Google’s BigTable
  • Uses Hadoop’s HDFS as storage
  • Map/reduce with Hadoop
  • Query predicate push down via server side scan and get filters


  • Written in: C and C++mysql
  • License: OpenSource
  • Protocol: HTTP
  • Free to use
  • Great Performance
  • Very user-friendly
  • Incredible security
  • Scalable
  • Works with many operating systems
  • Supports many development interfaces


  • Written in: C and C++
  • License: PULA
  • Protocol: HTTP
  • Very feature rich
  • Highly reliable
  • Flashback technology
  • Capable of running large ILTB and VLDBs

Out of all above MySQL and Oracle are most popular.

When looking at the popularity of MySQL vs. Oracle, it’s important to note what each is used for most. Oracle is sued more for larger enterprises, while MySQL is used for smaller projects.

Out of the two, MySQL is the most popular. Since it’s used with WordPress, which is the most popular content management system for blogging and building websites, its use more often than Oracle.

However, for larger enterprises, Oracle is by far the more popular choice. Even though MySQL is used with larger sites, such as Facebook and YouTube, it’s not as popular with larger enterprises as Oracle.

If you have a choice between MySQL vs. Oracle, you will need to look at the specific project to make this decision.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s