My name is Doug Judd and I'm the CEO of Hypertable, Inc. I'm also the original creator and current maintainer of the project. Today I'm going to present an architectural overview of Hypertable within the context of some of the other popular scalable database designs. I'm also going to present some preliminary results from a performance evaluation that we're in the process of doing, comparing Hypertable with HBase.
About three years ago, I was working as an architect at Zvents, a local search engine. At the time we were trying to become the "Google" of local search. This meant collecting large and growing amounts of click log and query log data, doing analytics on that data, and using the results to fuel our ranking, recommendation, and ad targetting systems. At the time Hadoop existed, which povided the scalable filesystem and the MapReduce framework, but there was no scalable open source solution for delivering large data sets to live applications. So we decided to do an implementation and Bigtable was the obvious choice. We decided to do it open source and reap all of the benefits that the open source development model has to offer. A big focus of the project has been on optimum performance and the reason is simple. Efficiency gains scale linearly with the system, which translates to reduced hardware to deliver the same capacity. To that end, we chose C++ as the implementation language. Though the system is implemented in C++, we have a Thrift interface that provides language bindings for all popular high-level languages.
Describe the 360 degree panoramic view feature of Google Maps
In â07, Google was running 100,000 MapReduce jobs and processing 20 petabytes daily
Describe the 360 degree panoramic view feature of Google Maps
Describe the 360 degree panoramic view feature of Google Maps