By GUI app, I meant, a browser based application that's written in GWT. For
example, let's say an application that allows users to view logs such as,
application server logs or 'click tracking logs' etc. These logs are HUGE,
so our requirement is to allow users to view a month worth of data - which
is still HUGE! The application would allow users to 'slice and dice' data
the way they want, so it will have various filters. Should we access HBase
directly from the backend in real time? Anyone has any performance related
experiences to share?
Thanks again for your time.
On Thu, Feb 3, 2011 at 2:53 PM, Ryan Rawson <[EMAIL PROTECTED]> wrote:
> I think the answer is 'it depends'. What exactly is a "GUI app"
> anyways these days? The wording is a little vague to me, does that
> include things like amazon.com and google reader? Or is it limited to
> things like Firefox, and desktop applications?
> I think ultimately the only thing that is a must for HBase is either a
> need or a future need for large data. You could use HBase on a single
> node in production, but that is defeating the point. So unless you
> have enough data to justify multi machine deployments, perhaps flat
> On Thu, Feb 3, 2011 at 2:48 PM, Something Something
> <[EMAIL PROTECTED]> wrote:
> > Is it advisable to use HBase as a backend for a GUI app or is HBase more
> > storing huge amounts of data used mainly for data analysis in
> > non-online/batch mode? In other words, after storing data on HBase do
> > people extract the summary and store it in a SQL database for quick
> > retrieval by GUI? Or is 'SQL' a really bad word on this mailing list ;)