In Days 1 and 2, we got a lot of hands-on experience using HBase in stand-alone mode. Our experimentation so far has focused on accessing a single local server. In reality, if you choose to use HBase, you’ll want to have a good sized cluster in order to realize the performance benefits of its distributed architecture.
Here in Day 3, we’ll turn our attention toward operating and interacting with a remote HBase cluster. First we’ll develop a client application in Ruby and connect to our local server using a binary protocol called Thrift. Then we’ll bring up a multinode cluster with a cloud service provider—Amazon EC2—using a cluster management technology called Apache Whirr.