My thinking is around separation of concerns - at an OU level not just at a system integration level. Walrus gives me a consistent, usable abstraction layer to transparently substitute the storage implementation - for example from symmetrix <--> isilon or anything in between. Walrus is storage subsystem agnostic, so it need not be configured for inconsistency like the Amazon service it emulates.
Tight coupling for lock-in is a great commercial technique often seen with suppliers. But it is a bad one. Very bad. -----Original Message----- From: Andrew Purtell [mailto:apurt...@apache.org] Sent: Thu 5/13/2010 11:54 PM To: hbase-user@hadoop.apache.org Subject: RE: Using HBase on other file systems You really want to run HBase backed by Eucalyptus' Walrus? What do you have behind that? > From: Gibbon, Robert, VF-Group > Subject: RE: Using HBase on other file systems [...] > NB. I checked out running HBase over Walrus (an AWS S3 > clone): bork - you want me to file a Jira on that?
