Quantcast

NoSQL + Grails

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

NoSQL + Grails

Felipe Coutinho-2
Hello,

I'm working at a project that I will have a table with many rows and I need perfomace to query this table. I'm considering using a NoSQL database + Grails. Waht do you suggest?

Thank you,

Felipe.

--
Felipe Leal Coutinho
Website | Linkedin  | Facebook | Twitter

Softaware Soluções em Informática - Sócio-Administrador / Owner
Website | Linkedin  | Facebook | Twitter

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

bobbywarner
Mongo - http://grails.org/plugin/mongodb


Thanks,
Bobby
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

pledbrook
In reply to this post by Felipe Coutinho-2
> I'm working at a project that I will have a table with many rows and I need
> perfomace to query this table. I'm considering using a NoSQL database +
> Grails. Waht do you suggest?

That you check whether a standard relational database will satisfy
your performance needs. There are no shortcuts here I'm afraid. Also,
you need to decide whether you need referential integrity or not.
Also, how consistent does your database need to be? For example, if
you enable fsync in MongoDB, the performance apparently drops
significantly.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

Jordon Saardchit
Peter is right.  You should really take some significant time to analyze not only the current needs of your application, but future needs as well.  Going the NoSQL route isn't as cut and dry as just picking one.  Many of the implementations are designed to solve different problems.  Some things to consider before making a final decision would be:

* As peter said, referential integrity
* The ratio of reads vs writes to your data store.  Some nosql solutions are designed for higher volume writes or reads
* How important data consistency is to your application, if you require a clustered data store
* Transactions.  What operations will require them, and do you need them.
* The rate of growth your data, or if your data sets have a finite upper bound or not.  Are you expecting simple linear growth, or some rate of exponential growth.  In my experience, catching up to growth you aren't prepared for is the most difficult of problems in a growing company.

I've learned in my experience that rdbms and nosql has never been a 1 stop shop.  I've tended to require specific data store implementations to solve specific problems, thus resulting in a hybrid.  My only real advice is to not take advice from people who are religiously devoted to one solution.  Do your research, play around with solutions and do your own benchmarks if you have time.  And don't over complicate things if you don't have to.  Like Peter said, do you really need more than a simple RDBMS?

Jordon

On Oct 19, 2011, at 2:15 AM, Peter Ledbrook wrote:

>> I'm working at a project that I will have a table with many rows and I need
>> perfomace to query this table. I'm considering using a NoSQL database +
>> Grails. Waht do you suggest?
>
> That you check whether a standard relational database will satisfy
> your performance needs. There are no shortcuts here I'm afraid. Also,
> you need to decide whether you need referential integrity or not.
> Also, how consistent does your database need to be? For example, if
> you enable fsync in MongoDB, the performance apparently drops
> significantly.
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

Radim Kolar
I am really happy with cassandra nosql. it does not have native groovy
API. but it can handle very fast writes and reads (about 150k per second).

For some applications - like blog, you do not need transactions.
Cassandra can be distributed over several computers and it can even do
distributed counters. Migrating from SQL to Cassandra improved our app
response times about 15 times.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

Daniel Honig
Selecting a NO SQL store is far beyond what can answered within an e-mail reply.
However regardless of what CAP principals you can or cannot accept, I think many would agree that migrating to NoSQL is probably only justified after you have maxed out the conventional solution.

-dh

On Wed, Oct 19, 2011 at 11:14 AM, Radim Kolar <[hidden email]> wrote:
I am really happy with cassandra nosql. it does not have native groovy API. but it can handle very fast writes and reads (about 150k per second).

For some applications - like blog, you do not need transactions. Cassandra can be distributed over several computers and it can even do distributed counters. Migrating from SQL to Cassandra improved our app response times about 15 times.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

olivertynes
Just to piggyback on Daniel.

Starting out on NoSQL on a platform designed around the classical SQL
RDBMS sounds a bit weird. Migrating parts of your app to NoSQL is
suprisingly painless in grails, so unless you have some sort of very
specialized edge case I would say 90% of projects can just blindly
chose SQL and be happy with that for a long long time.

Personally I use SQL for the main data of the app and cache / store
query results / dynamic stuff in MongoDB, a solution that works
excellent.

-Oliver

On Wed, Oct 19, 2011 at 5:27 PM, Daniel Honig <[hidden email]> wrote:

> Selecting a NO SQL store is far beyond what can answered within an e-mail
> reply.
> However regardless of what CAP principals you can or cannot accept, I think
> many would agree that migrating to NoSQL is probably only justified after
> you have maxed out the conventional solution.
>
> -dh
>
> On Wed, Oct 19, 2011 at 11:14 AM, Radim Kolar <[hidden email]> wrote:
>>
>> I am really happy with cassandra nosql. it does not have native groovy
>> API. but it can handle very fast writes and reads (about 150k per second).
>>
>> For some applications - like blog, you do not need transactions. Cassandra
>> can be distributed over several computers and it can even do distributed
>> counters. Migrating from SQL to Cassandra improved our app response times
>> about 15 times.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>
>



--
*****
Oliver Tynes
Developer
Uni CIPR -- www.cipr.uni.no
55588266
*****

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: NoSQL + Grails

Felipe Coutinho-2
Thank you everyone!

Felipe.

--
Felipe Leal Coutinho
Website | Linkedin  | Facebook | Twitter

Softaware Soluções em Informática - Sócio-Administrador / Owner
Website | Linkedin  | Facebook | Twitter



On Wed, Oct 19, 2011 at 4:57 PM, Oliver Severin Tynes <[hidden email]> wrote:
Just to piggyback on Daniel.

Starting out on NoSQL on a platform designed around the classical SQL
RDBMS sounds a bit weird. Migrating parts of your app to NoSQL is
suprisingly painless in grails, so unless you have some sort of very
specialized edge case I would say 90% of projects can just blindly
chose SQL and be happy with that for a long long time.

Personally I use SQL for the main data of the app and cache / store
query results / dynamic stuff in MongoDB, a solution that works
excellent.

-Oliver

On Wed, Oct 19, 2011 at 5:27 PM, Daniel Honig <[hidden email]> wrote:
> Selecting a NO SQL store is far beyond what can answered within an e-mail
> reply.
> However regardless of what CAP principals you can or cannot accept, I think
> many would agree that migrating to NoSQL is probably only justified after
> you have maxed out the conventional solution.
>
> -dh
>
> On Wed, Oct 19, 2011 at 11:14 AM, Radim Kolar <[hidden email]> wrote:
>>
>> I am really happy with cassandra nosql. it does not have native groovy
>> API. but it can handle very fast writes and reads (about 150k per second).
>>
>> For some applications - like blog, you do not need transactions. Cassandra
>> can be distributed over several computers and it can even do distributed
>> counters. Migrating from SQL to Cassandra improved our app response times
>> about 15 times.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>
>



--
*****
Oliver Tynes
Developer
Uni CIPR -- www.cipr.uni.no
55588266
*****

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



Loading...