You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Dalia Sobhy <da...@hotmail.com> on 2012/02/18 14:25:18 UTC
Medical App
Hiii all,
I am developing a medical app but i have reached this:
1. For structured Data such as patient info, medical history...etc: i would use RDBMS.
2. For non-structured data such as scans, images, MRIs: i would use hbase "nosql database"
So is this new arch is good??
I need your opinions..
If so how could i link between both sql and nosql, how could i link data..
Sent from my iPhone
Re: Medical App
Posted by Ulrich Staudinger <us...@activequant.com>.
At the risk of being called snippy, if your main problem is how to link the
two, i wonder how you want to achieve getting the RDBMS structure right.
What about storing an entry ID in your RDBMS and putting the document under
the same entry ID (read row key) into your hbase?
cheers
On Sat, Feb 18, 2012 at 2:25 PM, Dalia Sobhy <da...@hotmail.com>wrote:
> Hiii all,
>
> I am developing a medical app but i have reached this:
> 1. For structured Data such as patient info, medical history...etc: i
> would use RDBMS.
> 2. For non-structured data such as scans, images, MRIs: i would use hbase
> "nosql database"
>
> So is this new arch is good??
> I need your opinions..
> If so how could i link between both sql and nosql, how could i link data..
>
> Sent from my iPhone
--
Ulrich Staudinger
<http://goog_958005736>http://www.activequant.com
Connect online: https://www.xing.com/profile/Ulrich_Staudinger
Re: Medical App
Posted by Alexander Lorenz <wg...@googlemail.com>.
Hi,
for unstructured data hbase, sqoop as connector between hbase and rmdbs.
as an rest interface for hbase you could use stargate. Oozie as framework for periodical jobs.
best,
Alex
sent via my mobile device
On Feb 18, 2012, at 11:17 PM, Dalia Sobhy <da...@hotmail.com> wrote:
> My usecase is developing a scalable medical App.
>
> This app has two main parts :
> 1. Patient's Info
> 2. Patient's Diagnosis, Imaging...etc.
> 3. How to link between them.
>
> I want to perform an API for developers to use...
>
> I want to use a NoSQL Database, because this is my thesis topic and I am stuck in it. I only have a couple of months time period to accomplish it.
>
> So what I want is a guidance which better suits my app, I will not perform a complete app because I have time shortage.
>
> > From: PJamack@consilium1.com
> > To: user@hive.apache.org
> > Date: Sat, 18 Feb 2012 14:58:06 -0500
> > Subject: Re: Medical App
> >
> > There are ways to integrate each, but you'll have to figure out what
> > actually matches and what doesn't. Maybe a customer id can link a medical
> > image, with their info, etc.
> > I've done a combo of MongoDB as the non structured OLTP, Postgres as the
> > RDBMS, and then
> > Utilizing Hadoop as the analytic portion. Maybe it was overkill but Hbase
> > wasn't that great of an option, so. You might also need to use something
> > like Solr to index the non structured data.
> >
> > These days many ETL tools like Pentaho Kettle, Talend, even Informatica
> > and
> > Spring Data-Hadoop have ways to integrate and connect. I'm in the process
> > of figuring out the Pentaho Kettle big data integration and will follow up
> > with anything I learn in making it easier to integrate the different data
> > pieces.
> >
> > Peter J
> >
> > On 2/18/12 5:25 AM, "Dalia Sobhy" <da...@hotmail.com> wrote:
> >
> > >Hiii all,
> > >
> > >I am developing a medical app but i have reached this:
> > >1. For structured Data such as patient info, medical history...etc: i
> > >would use RDBMS.
> > >2. For non-structured data such as scans, images, MRIs: i would use hbase
> > >"nosql database"
> > >
> > >So is this new arch is good??
> > >I need your opinions..
> > >If so how could i link between both sql and nosql, how could i link data..
> > >
> > >Sent from my iPhone
> >
RE: Medical App
Posted by Dalia Sobhy <da...@hotmail.com>.
My usecase is developing a scalable medical App.
This app has two main parts :1. Patient's Info2. Patient's Diagnosis, Imaging...etc.3. How to link between them.
I want to perform an API for developers to use...
I want to use a NoSQL Database, because this is my thesis topic and I am stuck in it. I only have a couple of months time period to accomplish it.
So what I want is a guidance which better suits my app, I will not perform a complete app because I have time shortage.
> From: PJamack@consilium1.com
> To: user@hive.apache.org
> Date: Sat, 18 Feb 2012 14:58:06 -0500
> Subject: Re: Medical App
>
> There are ways to integrate each, but you'll have to figure out what
> actually matches and what doesn't. Maybe a customer id can link a medical
> image, with their info, etc.
> I've done a combo of MongoDB as the non structured OLTP, Postgres as the
> RDBMS, and then
> Utilizing Hadoop as the analytic portion. Maybe it was overkill but Hbase
> wasn't that great of an option, so. You might also need to use something
> like Solr to index the non structured data.
>
> These days many ETL tools like Pentaho Kettle, Talend, even Informatica
> and
> Spring Data-Hadoop have ways to integrate and connect. I'm in the process
> of figuring out the Pentaho Kettle big data integration and will follow up
> with anything I learn in making it easier to integrate the different data
> pieces.
>
> Peter J
>
> On 2/18/12 5:25 AM, "Dalia Sobhy" <da...@hotmail.com> wrote:
>
> >Hiii all,
> >
> >I am developing a medical app but i have reached this:
> >1. For structured Data such as patient info, medical history...etc: i
> >would use RDBMS.
> >2. For non-structured data such as scans, images, MRIs: i would use hbase
> >"nosql database"
> >
> >So is this new arch is good??
> >I need your opinions..
> >If so how could i link between both sql and nosql, how could i link data..
> >
> >Sent from my iPhone
>
Re: Medical App
Posted by "Jamack, Peter" <PJ...@consilium1.com>.
There are ways to integrate each, but you'll have to figure out what
actually matches and what doesn't. Maybe a customer id can link a medical
image, with their info, etc.
I've done a combo of MongoDB as the non structured OLTP, Postgres as the
RDBMS, and then
Utilizing Hadoop as the analytic portion. Maybe it was overkill but Hbase
wasn't that great of an option, so. You might also need to use something
like Solr to index the non structured data.
These days many ETL tools like Pentaho Kettle, Talend, even Informatica
and
Spring Data-Hadoop have ways to integrate and connect. I'm in the process
of figuring out the Pentaho Kettle big data integration and will follow up
with anything I learn in making it easier to integrate the different data
pieces.
Peter J
On 2/18/12 5:25 AM, "Dalia Sobhy" <da...@hotmail.com> wrote:
>Hiii all,
>
>I am developing a medical app but i have reached this:
>1. For structured Data such as patient info, medical history...etc: i
>would use RDBMS.
>2. For non-structured data such as scans, images, MRIs: i would use hbase
>"nosql database"
>
>So is this new arch is good??
>I need your opinions..
>If so how could i link between both sql and nosql, how could i link data..
>
>Sent from my iPhone