Re: Meh.
Ha, you're not grasping the concept. While it's relatively easy to extract, load and duplicate your data between all the silos that generate and consume the data - you will end up with dataset duplication and a lot of ETL overhead (a jungle of data feeds). Our customers have application constellations where the same large dataset (that all app modules in different databases need to use) is duplicated over 20x. This is 20x storage cost, 20x ETL overhead and you will still not see the latest state of your data unless you set up & run real-time replication to all those 20 databases.
Gluent's approach allows you to not duplicate data in RDBMS & SAN storage at all, just keep it in Hadoop once and consume it with native SQL queries of your database - on demand, on the fly - without having to first load & duplicate data anywhere. And that's just part of the story - now as bulk of your incoming (or offloaded) data resides in Hadoop, we can transparently push the related processing down to Hadoop, close to data as well, radically reducing the CPU licenses and SAN storage throughput needed for your RDBMS. Exporting/importing files around is not data virtualization.
See you in 20 years! :-)
Biting the hand that feeds IT
