Cloud Databases

Joab Jackson, in his "Cloud computing leaving relational databases behind" article, makes some pretty interesting points on the incompatibility of relational databases with cloud-based infrastructures. He first list the various cloud optimized databases:

• Google's Bigtable,
• Amazon's SimpleDB,
• 10Gen's Mongo,
• AppJet's AppJet database, and
• Oracle open-source BerkelyDB.

And then notes that they all have cloud computing-specific characteristics.

• They can be run in distributed environments,
• None of them are transactional in nature, and
• They all sacrifice some advanced querying capability for faster performance.

Since the national security community literally lives and dies by the information in their relational databases, what does that mean if the community adopts cloud technology in order to benefit from the scalability and economy?

The key issue here is that in cloud implementations, database material is spread across different locations. Executing complex queries with relational databases across vast geographic distances can slow response time. It is also difficult to design and maintain an architecture to replicate relational data across different locations and keep that data in sync if one location goes down.

Since cloud implementations are seemingly the wave of the future, community CIO's and analyst alike need to start thinking about the implications of the coming transition from relational databases today.