For me, early on, it was getting my head around the datastore structure (or, more aptly, the LACK of structure). I was migrating over a large SQL table, and it was highly inefficient as one big model in GAE. I ended up breaking it down into many different models (entity groups) with ReferenceProperty, and had to think about how the properties would be grouped to keep the datastore calls small and fast.
Man, it makes such perfect sense now, but I had trouble understanding at the beginning. And of course, you need to start and end with optimizing code, caching responses, etc. to keep the costs reasonable. And explain that their code will be MUCH better after optimizing it for GAE. They will "unlearn" some bad coding habits, and never look at app development the same again. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
