On Sun, Jan 31, 2016 at 5:14 AM, Dhanunjaya Naidu. Yandrapu <
[email protected]> wrote:

> Hi,
>
> I am new to Google cloud and have few question. I have few questions. I
> would very much appreciate if you could answer them.
>
> we are planning to use appengine, datastore/cloud storage and golang for
> my next project.Here are my questions:
>
>    1. Currently planning to use appengine but might move to compute
>    engine at a later point of time. is it possible to move from appengine to
>    compute engine and seamlessly access datastore and cloud storage from
>    compute engine(in the same project)?
>
>
Google Cloud Datastore,
https://cloud.google.com/datastore/docs/concepts/overview?hl=en , is
accessible from GCE and other platforms. However it's not "seamless" with
the very similar feature of App Engine. Cloud Storage, OTOH, *is*
"seamless" across all platforms (but has completely different features from
a database).



>
>    1. Are there any limits on datastore entity kinds per project?
>
> The relevant limits is, 200 indices (beyond automatic
single-property-ascending ones). If you do any query requiring filtering or
ordering on more than one property, that will require an index for each
kind you query that way.


>
>    1. I would also like to know your thoughts on the following design
>    choice for the data model in datastore. We are planning to use name-spaces
>    for multi-tenancy and we have around 100 entity kinds. I am wondering if 
> *Approach
>    2 *has any advantages over *Approach 1* in terms of query performance
>    or reducing the query cost or deleting all the entities of a particular
>    tenant
>       - *Approach 1*: have 100 entity kinds and use name-spaces for
>       tenant isolation. So we always have 100 entity kinds regardless of the
>       number of tenants
>       - *Approach 2*: use name-spaces for tenant isolation and append
>       tenant ID for each kind, so if we have 10,000 tenants, we will have 1
>       million entity kinds.
>
>
I see no advantage to approach 2. It would surely stop you from using any
but the most elementary queries due to the limit on number of indices.


Alex



> thanks in advance.
>
>
> --
> 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 https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/35c69f13-b407-4f6a-b14a-ad1303b49a20%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/35c69f13-b407-4f6a-b14a-ad1303b49a20%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAE46Be987DuAmmKZOFyke6C-yXOND2Z_cYEiuZA5XSFNkykRBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to