I don't think I would try to use a single-node HBase cluster to replace a MySQL database. HBase has a sweet spot, both in terms of scale and data access patterns. In general, it should not be viewed as a drop in replacement to MySQL. My questions to you would be:
1) How much data do you need to store? 2) What are your access patterns? Lots of joins, individual row lookups, range scans, etc. -Joey On Mon, Nov 14, 2011 at 1:54 AM, Em <[email protected]> wrote: > Hello list, > > I was asked whether it is a good idea to replace the M in LAMP with > Hbase as well as the P with Java-Servlet (i.e. Tomcat) so that you run > your webserver, your hbase-instance, hadoop etc. on the same machine. > > Are the differences compared to a LAMP-Stack in terms of performance large? > > It is clear that a lot of benefits like redundancy etc. are not > available in this setup. However if the idea and userbase grows you can > quickly add these features to the environment by just setting up new > machines and connect them with eachother. > > When I was asked about this I had no answer. > Hopefully you can bring light into this! > > Kind regards, > Em > -- Joseph Echeverria Cloudera, Inc. 443.305.9434
