Can I create multiple GAE projects for microservices of a single Web application? [cross post]
This is a cross post from https://groups.google.com/d/msg/google-appengine/_a_aHExiZ-A/2oKfuEb9CQAJ
I want to create a Web application with microsevices architecture by using creation of a multiple GAE projects.
https://cloud.google.com/appengine/docs/standard/go/microservices-on-app-engine introduces two types of a way to realize microservices; "multiple services" and "multiple projects".
However, according to Google Cloud Platform Terms of Service (https://cloud.google.com/terms/) ...
3.3 Restrictions
Customer will not, and will not allow third parties under its control to
(d) create multiple Applications, Accounts, or Projects to simulate or act as a single Application, Account, or Project (respectively) or otherwise access the Services in a manner intended to avoid incurring Fees or exceed usage limits or quotas
I think I can't create multiple GAE projects for microservices to build a single Web Application because a such as the action againsts 3.3 of the Terms of Service.
But the document introduces that approarch. I've puzzled about it.
Can I create multiple GAE projects for microservices of a single Web application regardless of the description of the terms?
google-app-engine google-cloud-platform microservices
edited Dec 11 '18 at 11:58
Maxim
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
add a comment |
This is a cross post from https://groups.google.com/d/msg/google-appengine/_a_aHExiZ-A/2oKfuEb9CQAJ
I want to create a Web application with microsevices architecture by using creation of a multiple GAE projects.
https://cloud.google.com/appengine/docs/standard/go/microservices-on-app-engine introduces two types of a way to realize microservices; "multiple services" and "multiple projects".
However, according to Google Cloud Platform Terms of Service (https://cloud.google.com/terms/) ...
3.3 Restrictions
Customer will not, and will not allow third parties under its control to
(d) create multiple Applications, Accounts, or Projects to simulate or act as a single Application, Account, or Project (respectively) or otherwise access the Services in a manner intended to avoid incurring Fees or exceed usage limits or quotas
I think I can't create multiple GAE projects for microservices to build a single Web Application because a such as the action againsts 3.3 of the Terms of Service.
But the document introduces that approarch. I've puzzled about it.
Can I create multiple GAE projects for microservices of a single Web application regardless of the description of the terms?
google-app-engine google-cloud-platform microservices
edited Dec 11 '18 at 11:58
Maxim
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
add a comment |
This is a cross post from https://groups.google.com/d/msg/google-appengine/_a_aHExiZ-A/2oKfuEb9CQAJ
I want to create a Web application with microsevices architecture by using creation of a multiple GAE projects.
https://cloud.google.com/appengine/docs/standard/go/microservices-on-app-engine introduces two types of a way to realize microservices; "multiple services" and "multiple projects".
However, according to Google Cloud Platform Terms of Service (https://cloud.google.com/terms/) ...
3.3 Restrictions
Customer will not, and will not allow third parties under its control to
(d) create multiple Applications, Accounts, or Projects to simulate or act as a single Application, Account, or Project (respectively) or otherwise access the Services in a manner intended to avoid incurring Fees or exceed usage limits or quotas
I think I can't create multiple GAE projects for microservices to build a single Web Application because a such as the action againsts 3.3 of the Terms of Service.
But the document introduces that approarch. I've puzzled about it.
Can I create multiple GAE projects for microservices of a single Web application regardless of the description of the terms?
google-app-engine google-cloud-platform microservices
edited Dec 11 '18 at 11:58
Maxim
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
This is a cross post from https://groups.google.com/d/msg/google-appengine/_a_aHExiZ-A/2oKfuEb9CQAJ
I want to create a Web application with microsevices architecture by using creation of a multiple GAE projects.
https://cloud.google.com/appengine/docs/standard/go/microservices-on-app-engine introduces two types of a way to realize microservices; "multiple services" and "multiple projects".
However, according to Google Cloud Platform Terms of Service (https://cloud.google.com/terms/) ...
3.3 Restrictions
Customer will not, and will not allow third parties under its control to
(d) create multiple Applications, Accounts, or Projects to simulate or act as a single Application, Account, or Project (respectively) or otherwise access the Services in a manner intended to avoid incurring Fees or exceed usage limits or quotas
I think I can't create multiple GAE projects for microservices to build a single Web Application because a such as the action againsts 3.3 of the Terms of Service.
But the document introduces that approarch. I've puzzled about it.
Can I create multiple GAE projects for microservices of a single Web application regardless of the description of the terms?
google-app-engine google-cloud-platform microservices
google-app-engine google-cloud-platform microservices
edited Dec 11 '18 at 11:58
Maxim
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
edited Dec 11 '18 at 11:58
Maxim
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
edited Dec 11 '18 at 11:58
Maxim
1,553211
edited Dec 11 '18 at 11:58
Maxim
1,553211
edited Dec 11 '18 at 11:58
Maxim
1,553211
1,553211
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
asked Nov 26 '18 at 8:35
Kousuke EbiharaKousuke Ebihara
262
262
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
IMHO your intention is to implement a certain architecture, not to avoid incurring Fees or exceed usage limits or quotas.
The difference should, I think, be pretty obvious for the tech-savvy GAE personnel checking out one's actual GAE usage - your microservices from different projects won't be doing the same thing only in a different context, each "contributing" their quota limits towards a larger effective quota.
Yes, it's true, the free quotas of the projects are combined, but that's just a side effect, not the primary goal.
Even if the apps/services are doing the same thing, there may be OK usage cases. A couple of such examples from Google documentation and referenced in SO posts:
- global deployment of nodejs with app engine as described in the docs
- Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But I'd check first if there is a good reason for using separate apps instead of separate services. Just to reduce potentially unnecessary friction.
And if you want to be super-certain, just contact Google with your particular use case and reasoning supporting it.
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...the limitation applies only if a "third party under [your] control" performs the operationIs that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.
– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53477270%2fcan-i-create-multiple-gae-projects-for-microservices-of-a-single-web-application%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
IMHO your intention is to implement a certain architecture, not to avoid incurring Fees or exceed usage limits or quotas.
The difference should, I think, be pretty obvious for the tech-savvy GAE personnel checking out one's actual GAE usage - your microservices from different projects won't be doing the same thing only in a different context, each "contributing" their quota limits towards a larger effective quota.
Yes, it's true, the free quotas of the projects are combined, but that's just a side effect, not the primary goal.
Even if the apps/services are doing the same thing, there may be OK usage cases. A couple of such examples from Google documentation and referenced in SO posts:
- global deployment of nodejs with app engine as described in the docs
- Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But I'd check first if there is a good reason for using separate apps instead of separate services. Just to reduce potentially unnecessary friction.
And if you want to be super-certain, just contact Google with your particular use case and reasoning supporting it.
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...the limitation applies only if a "third party under [your] control" performs the operationIs that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.
– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
add a comment |
IMHO your intention is to implement a certain architecture, not to avoid incurring Fees or exceed usage limits or quotas.
The difference should, I think, be pretty obvious for the tech-savvy GAE personnel checking out one's actual GAE usage - your microservices from different projects won't be doing the same thing only in a different context, each "contributing" their quota limits towards a larger effective quota.
Yes, it's true, the free quotas of the projects are combined, but that's just a side effect, not the primary goal.
Even if the apps/services are doing the same thing, there may be OK usage cases. A couple of such examples from Google documentation and referenced in SO posts:
- global deployment of nodejs with app engine as described in the docs
- Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But I'd check first if there is a good reason for using separate apps instead of separate services. Just to reduce potentially unnecessary friction.
And if you want to be super-certain, just contact Google with your particular use case and reasoning supporting it.
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...the limitation applies only if a "third party under [your] control" performs the operationIs that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.
– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
add a comment |
IMHO your intention is to implement a certain architecture, not to avoid incurring Fees or exceed usage limits or quotas.
The difference should, I think, be pretty obvious for the tech-savvy GAE personnel checking out one's actual GAE usage - your microservices from different projects won't be doing the same thing only in a different context, each "contributing" their quota limits towards a larger effective quota.
Yes, it's true, the free quotas of the projects are combined, but that's just a side effect, not the primary goal.
Even if the apps/services are doing the same thing, there may be OK usage cases. A couple of such examples from Google documentation and referenced in SO posts:
- global deployment of nodejs with app engine as described in the docs
- Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But I'd check first if there is a good reason for using separate apps instead of separate services. Just to reduce potentially unnecessary friction.
And if you want to be super-certain, just contact Google with your particular use case and reasoning supporting it.
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
IMHO your intention is to implement a certain architecture, not to avoid incurring Fees or exceed usage limits or quotas.
The difference should, I think, be pretty obvious for the tech-savvy GAE personnel checking out one's actual GAE usage - your microservices from different projects won't be doing the same thing only in a different context, each "contributing" their quota limits towards a larger effective quota.
Yes, it's true, the free quotas of the projects are combined, but that's just a side effect, not the primary goal.
Even if the apps/services are doing the same thing, there may be OK usage cases. A couple of such examples from Google documentation and referenced in SO posts:
- global deployment of nodejs with app engine as described in the docs
- Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But I'd check first if there is a good reason for using separate apps instead of separate services. Just to reduce potentially unnecessary friction.
And if you want to be super-certain, just contact Google with your particular use case and reasoning supporting it.
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
answered Nov 26 '18 at 12:06
Dan CornilescuDan Cornilescu
29.9k113767
29.9k113767
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...the limitation applies only if a "third party under [your] control" performs the operationIs that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.
– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
add a comment |
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...the limitation applies only if a "third party under [your] control" performs the operationIs that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.
– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
2
2
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
GCP support here. I would like to reiterate that the limitation applies only if a "third party under [your] control" performs the operation. I agree with Dan Cornilescu: you should be sure that using separate projects instead of services will be the optimal architecture and why.
– Rubén C.
Nov 26 '18 at 14:08
@RubénC. Thanks, but...
the limitation applies only if a "third party under [your] control" performs the operation Is that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.– Kousuke Ebihara
Nov 26 '18 at 16:53
@RubénC. Thanks, but...
the limitation applies only if a "third party under [your] control" performs the operation Is that for sure? The terms of service says "Customer will not, and will not allow third parties under its control to". I recognized that this restriction is also applied to me. I think I can explain about the reason of choosing separating projects approach. I'll feel relieved if Google gives me a chance to excuse about it when my app behaves suspícious actions for Google.– Kousuke Ebihara
Nov 26 '18 at 16:53
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
Based on our discussion, I guess that you are on a development stage. Is the right time to contact support to deeply discuss your pipeline if you are not entirely sure about the best option (if you don't want to discuss it publicly, which we fully understand). Please create a support case or let me know if you want me to create a public issue on your behalf.
– Rubén C.
Nov 27 '18 at 9:28
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.
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%2f53477270%2fcan-i-create-multiple-gae-projects-for-microservices-of-a-single-web-application%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
