A bigger reason, is almost certainly AppEngine existed before BigQuery. Also not really sure see that BigQuery is an AppEngine 'offering' as such. Its part of Googles Cloud offerings, but not specifically AppEngine.
Also BigQuery is supposedly powered by Dremel - which is suited for read-only data. When it launched it could only create a BigQuery table by importing a big file. No updates. Its only later that it began gain on-demand appending. On Wed, Jun 26, 2013 at 5:04 AM, Aniket Bhatnagar < aniket.bhatna...@gmail.com> wrote: > Considering BigQuery is an AppEngine offering, it seems like a natural fit > to store indexes. However, Datastore uses BigTable to store indexes. Why is > that so? > > One possible explanation provided on Quora[1] is that BigQuery is not a > right fit for heavy write scenario. If so, what is the recommended rate at > which BigQuery can accept data? > > References : > > [1] > http://www.quora.com/Google-App-Engine/Why-does-Google-App-Engine-Datastore-uses-BigTable-to-store-indexes-instead-of-using-BigQuery > > -- > 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 google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
