You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Erik Bengtson <er...@jpox.org> on 2009/10/19 11:52:13 UTC
Re: Minutes: JDO TCK Conference Call Friday, July 11, 9 am PDT
>Attendees: Michelle Caisse, Richard Schilling, Craig Russell
>An interesting option for a JDO implementation is to use a RESTful
>service like Amazon S3 or memcached for the back end. Some obvious
>issues are transactions, object identity, and query. But having an
>object front end for these would have clear productivity benefits
>compared to a user writing the entire thing by hand (tools are pretty
>simple for accessing data from these services).
It took more than a year, but DataNucleus now supports Amazon S3.
Re: Minutes: JDO TCK Conference Call Friday, July 11, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Excellent!
Craig
On Oct 19, 2009, at 2:52 AM, Erik Bengtson wrote:
>> Attendees: Michelle Caisse, Richard Schilling, Craig Russell
>
>> An interesting option for a JDO implementation is to use a RESTful
>> service like Amazon S3 or memcached for the back end. Some obvious
>> issues are transactions, object identity, and query. But having an
>> object front end for these would have clear productivity benefits
>> compared to a user writing the entire thing by hand (tools are pretty
>> simple for accessing data from these services).
>
> It took more than a year, but DataNucleus now supports Amazon S3.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!