Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4678EFE84 for ; Mon, 25 Mar 2013 19:30:50 +0000 (UTC) Received: (qmail 20105 invoked by uid 500); 25 Mar 2013 19:30:49 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 20058 invoked by uid 500); 25 Mar 2013 19:30:49 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 20050 invoked by uid 99); 25 Mar 2013 19:30:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 19:30:49 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bharathravi1@gmail.com designates 209.85.215.48 as permitted sender) Received: from [209.85.215.48] (HELO mail-la0-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 19:30:44 +0000 Received: by mail-la0-f48.google.com with SMTP id fq13so11913231lab.7 for ; Mon, 25 Mar 2013 12:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=3K17KpHAlK3HWuOOQtVsc6CNOqux8WgMrDyA9gg2KkM=; b=b7yKHYhvuH7s5QHKyUye2nD0MjYU6/UnCAvqWvqORTZSImtCReG9Rlf2wXm6NLdSim tPvDI4LdJbndBJzqheaw7L61xkU0+EWL1+f/EAbvNAKEgeZW/ixfUsogawVbgNV99gBJ ikWHdc6gxEflBM9aAv2pBos3uUhxTkftWAMJ7+J2ccWyBCR0Nzu/2+VReABSYQXoMoW8 zHsr9g3zHmYHFBcdumDB1GbEmtTEA+mQAU9eH4Yzy8CqEFCYpfFChvOLD4AHnyrEhqJT NbdsftVwA1w3ZW2oBObmkzb4dbJL3MPqRohrovAWCiWltK7143WkZYXEZOedgQ0V8C5k fGhQ== X-Received: by 10.112.88.5 with SMTP id bc5mr6726223lbb.50.1364239822704; Mon, 25 Mar 2013 12:30:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.43.41 with HTTP; Mon, 25 Mar 2013 12:30:02 -0700 (PDT) From: Bharath Ravi Date: Mon, 25 Mar 2013 15:30:02 -0400 Message-ID: Subject: Are there applications that directly use HBase's cache? To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d04016b49055be904d8c4d677 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04016b49055be904d8c4d677 Content-Type: text/plain; charset=ISO-8859-1 Hi HBase-dev, I'm working on improving caching in HBase as a part of academic research. I was wondering if you could help me answer some "how HBase is used" questions. 1.Are there instances of real-time applications that rely on HBase's datanode caching directly? I realize that many real-time applications employ a caching layer (like memcached) in between their stores and front-ends. Are there cases where HBase is used directly without an intermediate caching layer? 2. If so, why is an intermediate caching layer not employed? Note: by "real-time", I mean workloads that require immediate responses to a user: say a web application or real-time analytics (unlike MapReduce jobs that may be long running over several hours). Any advice would be greatly appreciated! Thanks, -- Bharath Ravi --f46d04016b49055be904d8c4d677--