My two cents is MongoDB. If you're going after speed and ease of
deployment, a monolithic application will almost always be easier to start
with than a component-based approach.
MongoDB also offers secondary indices, hierarchical data model and GridFS
for large image storage. You could also look at Riak 1.0 or earlier (1.1
removes Luwak support), which is somewhat similar and has the nice concept
of links built into their basic interface for use with map reduce jobs etc.
Of course, if you're not really going to bring it to any kind of scale,
you'd probably have much smoother time just storing everything in MySQL.
2012/2/18 Dalia Sobhy <[EMAIL PROTECTED]>
> 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.
> > Date: Sat, 18 Feb 2012 14:07:34 -0800
> > Subject: Re: Hbase vs MongoDB
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Can you please provide more information about your use case? It would
> > be helpful if you provided more information about specifically what you
> > trying to assess.
> > While I don't have MongoDB specific experience, I'm sure some here do.
> > However, it is very difficult to be helpful when you ask such a generic
> > question.
> > thanks,
> > Jacques
> > 2012/2/18 Dalia Sobhy <[EMAIL PROTECTED]>
> > >
> > > Could anyone help Hbase vs MongoDB??