db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: HDFS?
Date Sat, 20 Mar 2010 08:54:09 GMT
geoffrey hendrey <geoff.hendrey@gmail.com> writes:

> It could be interesting to have the roll-forward replication logs written to
> HDFS where they will be automatically replicated, then the Derby slave can
> read the roll-forward log out of HDFS. Storage of backups is another place

Data point: the current Derby replication works by sending the log
records to a slave already, but currently only to one
slave. Unfortunately, the Derby slave cannot yet even field read-only
queries (since technically it is in a recovery phase in slave mode)
which would allow an interesting scaling capabilities when combined
with HDFS.  (And not symmetrical replication, of course, i.e. dual

What advantage do you see in storing lobs in HBase?

This are interesting topics to investigate.


> where HDFS might play well. Another idea would be to provide blob storage in
> HBase. I don't see any conflict between wanting to use HBase and Derby,
> since they really do different things. And in fact, it would be really cool
> to see Derby *using* HBase for things like Blob Storage.
> It's just a random thought; but HDFS is really an amazing piece of
> engineering and it would be interesting to see it leveraged by Derby. In
> many "web scale" computing environments, it seems like Hadoop and HDFS are
> becoming quite ubiquitous.
> -- 
> http://nextdb.net - RESTful Relational Database
> http://www.nextdb.net/wiki/en/REST

Dag H. Wanvik, staff engineer
Sun Microsystems, Java Core and Desktop - Java DB/Derby
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101
Sun IM: dw136674, Yahoo IM: dag_h_wanvik

View raw message