Relational databases also require indexes, however NoSQL indexes are much harder to generate and costly
You generally have to build with precision when developing with NoSQL, always knowing what you want and how you want it, build the models and indexes / systems for that There are also many other gotchas you learn with NoSQL - or AppEngine specifically But I will say this, I've never felt hopeless while using AppEngine, there is always someone out there to help with issues, or an efficient documentation Long story short, I've been using AppEngine at large scale for a while now, I would suggest it (The taskqueue system is also pretty strong, you can easily build a mapping task (map of mapreduce) and iterate over all entities in a relatively short time, so if costs are not a big issue, you can always iterate over everything instead of running a flexible relational db query that you would do otherwise) (Issues also happen, but there is always the soothing fact that someone else solves them at scale, however, since you are intending for a corporate usage, you might take the responsibility yourself and build a custom system, would be much harder, much more costly) I'm guessing this isn't the detailed reply you were looking for, but just my .02 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
