looks interesting. I think I will give this a try. Can someone give any advice on doing full-text search over datastore entities? Compass+lucene is by far the heaviest part of my application.
On Wed, Mar 31, 2010 at 3:36 PM, John Patterson <jdpatter...@gmail.com>wrote: > > On 31 Mar 2010, at 17:58, Blake Caldwell wrote: > >> From the few hours I've spent with Twig, it seems easier - not >> harder than JDO for everything I'm doing. >> > > Nice to hear. You should get improved in ease of use from all of the > non-standard persistence interfaces designed specifically at the datastore - > just choose the features you need. Twigs ObjectDatastore aims to be as > efficient as hand coded low-level solutions with no startup overhead. > Unlike some of the other frameworks there is no "registration" process for > your data model classes - each class is analyzed the first time it is used > per server instance and the meta-data is cached for the duration of the > instance. > > One user found that queries which had to be run as tasks previously with > JDO could now be calculated on the fly in real time by using the > ObjectDatastore. > > Performance can be compared directly to JDO - I believe that Twig is the > only option which allows you to reuse you stored JDO data - correct me if I > am wrong on that. > > > If you want to use JPA or >> JDO because you're already familiar with them, that's great and all, >> but the mapping to BigTable isn't that straight forward, so cramming >> the framework on top might not be the answer. >> >> Create a data store tier, wrap all Twig/Objectify logic in there, and >> while your app won't be as portable as if you were using JDO, it'll >> perform better, use less resources, and not be terribly dificult to >> port later on, if you have to. >> > > Exactly. If you ever find yourself creating DTO's to abstract away details > of the persistence framework you use then consider that data models in Twig > *are* your DTOs - they have no dependencies at all. Pure POJOs which are > really simple to port to any persistence interface you choose. > > It also makes working with GWT a breeze because you can send a whole object > graph over the wire without having to fetch each item by Key (or Key<T>) > > >> My $0.02 >> >> > $0.04 total > > -- > 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 > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
