We are working on porting an application from a MySQL solution to HBase. There is info at http://www.ripe.net/ris/index.html. It's pretty academic (mostly interesting for large network operators and people investigating IP hijacking and the like). We basically aggregate data collected at several internet exchanges.
Point is we are currently at the limit of scaling the MySQL solution and our HBase prototype has no problem with the load. Whenever new data comes in, we do a read-modify-write on existing records, so it's not only appending data. Querying is also pretty much random access. So the usage pattern is not unlike what you could expect in typical web app scenarios. Currently, our service can only provide answers for a three months time period; with HBase we aim to up that to several years. Some information we store still goes in MySQL. This is a small amount of data that maps better to the relational model (configuration, meta stuff, etc.). A combination of relational and non-relational, better scalable storage can work well. The development effort that goes into it, is in our experience relatively cheap compared to the effort of continuously scaling out a relational database. Friso On Jul 10, 2010, at 19:47 , Jean-Daniel Cryans wrote: > At stumbleupon, we have su.pr (url shortner / advertising platform) > that's totally based on HBase and has been in production for more than > a year. Also many other parts of our main product also rely on HBase. > > J-D > > On Sat, Jul 10, 2010 at 10:43 AM, S Ahmed <[email protected]> wrote: >> Its my impression that most people are using nosql solutions for things like >> statistic logging etc. >> >> Has anyone build a web application purely in hbase? e.g. Say an application >> like Blogger or Gmail or vBulletin type applications. >> >> Are these potential candidates for building ontop of a nosql data store? >>
