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: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> 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
> 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
> Peter J
> On 2/18/12 5:25 AM, "Dalia Sobhy" <[EMAIL PROTECTED]> 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