app-engine plugin: JDO vs. JPA persistence

[Alexander Orlov-4]

There are statements that JDO is mature in comparison to JPA and easier to handle in combination with GAE. Also JPA is a RDBM focused persistence layer which isn't the best approach for Google's non-relational BigTable data store. In contrast JDO isn't a RDBM focused and a more generic persistence layer implementation.

So which persistence technology should I use in combination with the app-engine plugin? Which technology has a brighter future?

Alex

[tomas lin]

Without considering the merits of each technology, I would recommend
JPA if you choose to use Grails for app-engine.

1. Graeme is actively developing the JPA-GORM plugin (
https://svn.codehaus.org/grails-plugins/grails-gorm-jpa/trunk/test/integration/org/grails/jpa/BasicPersistenceMethodsTests.groovy
)

2. JPA templates since 0.8 of app engine.




On Fri, May 29, 2009 at 11:48 PM, Alexander Orlov
<[hidden email]> wrote:

> There are statements that JDO is mature in comparison to JPA and easier to
> handle in combination with GAE. Also JPA is a RDBM focused persistence layer
> which isn't the best approach for Google's non-relational BigTable data
> store. In contrast JDO isn't a RDBM focused and a more generic persistence
> layer implementation.
>
> So which persistence technology should I use in combination with the
> app-engine plugin? Which technology has a brighter future?
>
> Alex
>

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

    http://xircles.codehaus.org/manage_email

[Alexander Orlov-4]

On Sat, May 30, 2009 at 1:43 AM, Tomas Lin <[hidden email]> wrote:

Without considering the merits of each technology, I would recommend
JPA if you choose to use Grails for app-engine.

1. Graeme is actively developing the JPA-GORM plugin (
https://svn.codehaus.org/grails-plugins/grails-gorm-jpa/trunk/test/integration/org/grails/jpa/BasicPersistenceMethodsTests.groovy
)

2. JPA templates since 0.8 of app engine.

I'm have tried 0.8.1 with JPA and it works well. But the most important question for me is: Which technology has the brighter future in Grails? JPA or JDO? Graeme?

Alex

[Graeme Rocher-3]

On Sat, May 30, 2009 at 2:26 AM, Alexander Orlov
<[hidden email]> wrote:

> On Sat, May 30, 2009 at 1:43 AM, Tomas Lin <[hidden email]> wrote:
>>
>> Without considering the merits of each technology, I would recommend
>> JPA if you choose to use Grails for app-engine.
>>
>> 1. Graeme is actively developing the JPA-GORM plugin (
>>
>> https://svn.codehaus.org/grails-plugins/grails-gorm-jpa/trunk/test/integration/org/grails/jpa/BasicPersistenceMethodsTests.groovy
>> )
>>
>> 2. JPA templates since 0.8 of app engine.
>
> I'm have tried 0.8.1 with JPA and it works well. But the most important
> question for me is: Which technology has the brighter future in Grails? JPA
> or JDO? Graeme?

Historically JPA/Hibernate have had and continue to have more
momentum. I see no reason why AppEngine supporting JDO is going to
change that.

Cheers
>
> Alex
>



--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[boardtc]

Following your screencast (http://grails.org/dist/screencasts/grails-appengine-screencast.mov) to setup a app-engine application you say that the plugin uses jdo by default and suggest to use it. If I read this post correctly it would appear to contradict that?

Thanks, Tom.

Graeme Rocher-3 wrote:

> On Sat, May 30, 2009 at 1:43 AM, Tomas Lin <[e-mail]> wrote:
>> Without considering the merits of each technology, I would recommend
>> JPA if you choose to use Grails for app-engine.
Historically JPA/Hibernate have had and continue to have more
momentum. I see no reason why AppEngine supporting JDO is going to
change that.

[tomas lin]

The screencast came out before the gorm-jpa plugin.

I think there is really no reason to choose JDO today unless you want
better documentation and don't plan to use the GORM features.

On Wed, Dec 9, 2009 at 11:39 AM, Tom Corcoran <[hidden email]> wrote:

>
> Following your screencast
> (http://grails.org/dist/screencasts/grails-appengine-screencast.mov) to
> setup a app-engine application you say that the plugin uses jdo by default
> and suggest to use it. If I read this post correctly it would appear to
> contradict that?
>
> Thanks, Tom.
>
>
> Graeme Rocher-3 wrote:
>>
>>> On Sat, May 30, 2009 at 1:43 AM, Tomas Lin <[hidden email]> wrote:
>>>> Without considering the merits of each technology, I would recommend
>>>> JPA if you choose to use Grails for app-engine.
>> Historically JPA/Hibernate have had and continue to have more
>> momentum. I see no reason why AppEngine supporting JDO is going to
>> change that.
>>
>
> --
> View this message in context: http://old.nabble.com/app-engine-plugin%3A-JDO-vs.-JPA-persistence-tp23788142p26708910.html
> Sent from the grails - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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