Google Cloud Datastore: Does multitenancy have any benefit at all?
up vote
2
down vote
favorite
Is datastore multitenancy bringing any benefit at all rather than logically separating the data of each tenant?
What's the difference of having a namespace per tenant rather than having data for all tenants i na single namespace?
Data is partitioned by projectId+ namespace right? This means that all the data within a single namespace will be located on the same disk.
google-app-engine 
google-cloud-datastore datastore asked Nov 22 at 15:27
Dan Dinu
13.8k185691
add a comment |
up vote
2
down vote
favorite
Is datastore multitenancy bringing any benefit at all rather than logically separating the data of each tenant?
What's the difference of having a namespace per tenant rather than having data for all tenants i na single namespace?
Data is partitioned by projectId+ namespace right? This means that all the data within a single namespace will be located on the same disk.
google-app-engine google-cloud-datastore datastore asked Nov 22 at 15:27
Dan Dinu
13.8k185691
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Is datastore multitenancy bringing any benefit at all rather than logically separating the data of each tenant?
What's the difference of having a namespace per tenant rather than having data for all tenants i na single namespace?
Data is partitioned by projectId+ namespace right? This means that all the data within a single namespace will be located on the same disk.
google-app-engine google-cloud-datastore datastore asked Nov 22 at 15:27
Dan Dinu
13.8k185691
Is datastore multitenancy bringing any benefit at all rather than logically separating the data of each tenant?
What's the difference of having a namespace per tenant rather than having data for all tenants i na single namespace?
Data is partitioned by projectId+ namespace right? This means that all the data within a single namespace will be located on the same disk.
google-app-engine google-cloud-datastore datastore google-app-engine google-cloud-datastore datastore asked Nov 22 at 15:27
Dan Dinu
13.8k185691
asked Nov 22 at 15:27
Dan Dinu
13.8k185691
asked Nov 22 at 15:27
Dan Dinu
13.8k185691
asked Nov 22 at 15:27
Dan Dinu
13.8k185691
asked Nov 22 at 15:27
Dan Dinu
13.8k185691
13.8k185691
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The data is located based on Project ID. You can have multiple tenants, but they are still in the same place, so there are no performance benefits.
There only benefits are for ease of data management, because your data is now segregated. You can export / delete / query them separately easier.
Data in the same project is co-located, regardless of namespace / tenancy.
answered Nov 23 at 16:24
Yasser Karout
714
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The data is located based on Project ID. You can have multiple tenants, but they are still in the same place, so there are no performance benefits.
There only benefits are for ease of data management, because your data is now segregated. You can export / delete / query them separately easier.
Data in the same project is co-located, regardless of namespace / tenancy.
answered Nov 23 at 16:24
Yasser Karout
714
add a comment |
up vote
1
down vote
accepted
The data is located based on Project ID. You can have multiple tenants, but they are still in the same place, so there are no performance benefits.
There only benefits are for ease of data management, because your data is now segregated. You can export / delete / query them separately easier.
Data in the same project is co-located, regardless of namespace / tenancy.
answered Nov 23 at 16:24
Yasser Karout
714
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The data is located based on Project ID. You can have multiple tenants, but they are still in the same place, so there are no performance benefits.
There only benefits are for ease of data management, because your data is now segregated. You can export / delete / query them separately easier.
Data in the same project is co-located, regardless of namespace / tenancy.
answered Nov 23 at 16:24
Yasser Karout
714
The data is located based on Project ID. You can have multiple tenants, but they are still in the same place, so there are no performance benefits.
There only benefits are for ease of data management, because your data is now segregated. You can export / delete / query them separately easier.
Data in the same project is co-located, regardless of namespace / tenancy.
answered Nov 23 at 16:24
Yasser Karout
714
answered Nov 23 at 16:24
Yasser Karout
714
answered Nov 23 at 16:24
Yasser Karout
714
answered Nov 23 at 16:24
Yasser Karout
714
714
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434108%2fgoogle-cloud-datastore-does-multitenancy-have-any-benefit-at-all%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
