do you have specific point to be careful in schema design? or pointers to any read? thanks.
On Sun, Nov 14, 2010 at 11:56 AM, andrew <aute...@gmail.com> wrote: > Just to reply to the point about persistence: > > > 1, GAE > > The benefits are obvious. However, it is also locking you in....you > > don't have much control over it. If you are unhappy later, you will > > have to redo the persistence layer and migrate data etc. > > If you are careful, and set it as a design objective from the start > then you can create a portable persistence layer. > > We do this using JDO and develope and test on GAE and Tomcat/MySql, > which I think will also allow us to cover EC2/S3 when we can get > around to it. > > -- > 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.
