Hi all. I recently decided to migrate away from JDO to one of the third party datastore frameworks. At first I had only heard about objectify, but after some further digging I found out about 5 other frameworks as well (Twig, SimpleDS, siena, slim3, cloud2db).
I was only interested in simple wrapper frameworks that acted as a convenience layer above the AppEngine low-level API. I _want_ the framework to expose the true nature of the datastore, but at the same time relieve the developer of the tedious tasks that's involved when working with the low-level API directly. It is much easier to work with the AppEngine datastore when its concepts, features, constraints and limitations are exposed directly. You can read more about the reasons for this in the article. This left me with objectify, Twig and SimpleDS. (siena and cloud2db are multi-platform and slim3 is more than just a datastore framework) I spent some time researching these when I got the idea to write an article about them. I contacted the authors for each framework and asked if they would be interested in participating. Passionate as they are, they agreed :-). Thanks to Jeff Schnitzer (objectify), John Patterson (Twig) and Ignacio Coloma (SimpleDS) for this. The goal is to publish two articles; one interview with the authors, and one where I solve some typical scenario with each framework. The interview article has now been published and can be found at http://borglin.net/gwt-project/?page_id=604 . The code example article will be posted sometime in the upcoming two weeks. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
