So may be you are all right I found Hbase really complex.. 
So what are other alternatives I am already using Hadoop as my backend system?

Kindly check apixio which is a similar medical system which adopts Hadoop so 
plz check and reply..

Bescause this is concerning my thesis part..

Thxx all for your sincere help :)

> From: doug.m...@explorysmedical.com
> To: user@hbase.apache.org
> Subject: Re: Important Question
> Date: Wed, 25 Jan 2012 21:23:13 +0000
> 
> 
> Hi there-
> 
> As someone who works with medical data I take such analysis very
> seriously, but according to the World Health Organization there were 608
> cases of measles reported in Egypt in 2011 (page 82).  Granted, these are
> probably incidence and not prevalence statistics, but the order of
> magnitude of data in your use-case is relatively small.
> 
> www.who.int/whosis/whostat/EN_WHS2011_Full.pdf
> 
> 
> Should you be considering something like MySQL?  Or Microsoft Access?  Or
> a spreadsheet?
> 
> One of the things that the overview points out...
> 
> http://hbase.apache.org/book.html#arch.overview
> 
> 
> ... is that HBase is really useful when you have a *lot* of data, but is
> also serious overkill and over-complexity if you don't.  I'm saying this
> because I'd like to support your epidemiological research, and also
> because I'd like to prevent you from having a bad HBase experience
> especially when the use-case doesn't seem to warrant it.
> 
> Doug
> 
> On 1/25/12 3:56 PM, "Dalia Sobhy" <dalia.mohso...@hotmail.com> wrote:
> 
> >
> >I will explain to u more Mike.
> >I am building a Software Oriented Architecture, I want my API to provide
> >some services such as Add/Delete Patients, Search for a patient by
> >name/ID, count the number of people who are suffering from measles in
> >Alexandria Egypt.
> >Something like that so I am wondering which best suits my API ??
> >
> >> To: dalia.mohso...@hotmail.com
> >> CC: user@hbase.apache.org; u...@hive.apache.org
> >> Subject: Re: Important Question
> >> From: mspre...@us.ibm.com
> >> Date: Wed, 25 Jan 2012 12:05:39 -0500
> >> 
> >> BTW, what do you mean by "realtime"?  Do you mean you want to run some
> >> non-trivial query quickly enough for some sort of interactive use?  Can
> >> you give us a feel for the sort of queries that interest you?
> >> 
> >> Thanks,
> >> Mike
> >> 
> >> 
> >> 
> >> From:   Dalia Sobhy <dalia.mohso...@hotmail.com>
> >> To:     "user@hbase.apache.org" <user@hbase.apache.org>
> >> Cc:     "u...@hive.apache.org" <u...@hive.apache.org>,
> >> "user@hbase.apache.org" <user@hbase.apache.org>
> >> Date:   01/25/2012 11:34 AM
> >> Subject:        Re: Important Question
> >> 
> >> 
> >> 
> >> So what about HBQL??
> >> And if i had complex queries would i get stuck with HBase?
> >> 
> >> Also can anyone provide me with examples of a table in RDBMS
> >>transformed 
> >> into hbase, realtime query and analytical processing..
> >> 
> >> Sent from my iPhone
> >> 
> >> On 2012-01-25, at 6:15 PM, bejoy...@yahoo.com wrote:
> >> 
> >> > Real Time.. Definitely not hive. Go in for HBase, but don't expect
> >>Hbase 
> >> to be as flexible as RDBMS. You need to choose your Row Key and Column
> >> Families wisely as per your requirements.
> >> > For data mining and analytics you can mount Hive table  over
> >> corresponding Hbase table and play on with SQL like queries.
> >> > 
> >> > 
> >> > 
> >> > Regards
> >> > Bejoy K S
> >> > 
> >> > -----Original Message-----
> >> > From: Dalia Sobhy <dalia.mohso...@hotmail.com>
> >> > Date: Wed, 25 Jan 2012 17:01:08
> >> > To: <user@hbase.apache.org>; <u...@hive.apache.org>
> >> > Reply-To: u...@hive.apache.org
> >> > Subject: Important Question
> >> > 
> >> > 
> >> > Dear all,
> >> > I am developing an API for medical use i.e Hospital admissions and
> >>all 
> >> about patients, thus transactions and queries and realtime data is
> >> important here...
> >> > Therefore both real-time and analytical processing is a must..
> >> > Therefore which best suits my application Hbase or Hive or another
> >> method ??
> >> > Please reply quickly bec this is critical thxxx a million ;)
> >> 
> >> 
> >                                       
> 
> 
                                          

Reply via email to