How to handle App and Database on multi-country?
I wonder how to handle multi-tenancy when you want to launch on multiple country.
Website like Adzuna or Jobtome, do they use one database/app/repo per country or only one for all? (
I think it's easier to maintain if you go for only one big app but does this make sense?
I have a similar case and I don't know what direction to choose...
php mysql web architecture devops
add a comment |
I wonder how to handle multi-tenancy when you want to launch on multiple country.
Website like Adzuna or Jobtome, do they use one database/app/repo per country or only one for all? (
I think it's easier to maintain if you go for only one big app but does this make sense?
I have a similar case and I don't know what direction to choose...
php mysql web architecture devops
1
Well, both would work. In my case, there are legal implications forwhere the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.
– YvesLeBorg
Nov 21 '18 at 15:41
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
1
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16
add a comment |
I wonder how to handle multi-tenancy when you want to launch on multiple country.
Website like Adzuna or Jobtome, do they use one database/app/repo per country or only one for all? (
I think it's easier to maintain if you go for only one big app but does this make sense?
I have a similar case and I don't know what direction to choose...
php mysql web architecture devops
I wonder how to handle multi-tenancy when you want to launch on multiple country.
Website like Adzuna or Jobtome, do they use one database/app/repo per country or only one for all? (
I think it's easier to maintain if you go for only one big app but does this make sense?
I have a similar case and I don't know what direction to choose...
php mysql web architecture devops
php mysql web architecture devops
asked Nov 21 '18 at 15:35
Olivier ZolettiOlivier Zoletti
1071212
1071212
1
Well, both would work. In my case, there are legal implications forwhere the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.
– YvesLeBorg
Nov 21 '18 at 15:41
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
1
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16
add a comment |
1
Well, both would work. In my case, there are legal implications forwhere the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.
– YvesLeBorg
Nov 21 '18 at 15:41
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
1
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16
1
1
Well, both would work. In my case, there are legal implications for
where the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.– YvesLeBorg
Nov 21 '18 at 15:41
Well, both would work. In my case, there are legal implications for
where the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.– YvesLeBorg
Nov 21 '18 at 15:41
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
1
1
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16
add a comment |
0
active
oldest
votes
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%2f53415512%2fhow-to-handle-app-and-database-on-multi-country%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53415512%2fhow-to-handle-app-and-database-on-multi-country%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
1
Well, both would work. In my case, there are legal implications for
where the data is at rest
, ie Canadian patient's data must be at rest on canuck turf, US->US, etc. So I have multiple DB's AND also multiple stacks to minimize 'data in-flight' intercept possibilities : DB is colocated with stack servers for the country. You chose what is best for you.– YvesLeBorg
Nov 21 '18 at 15:41
Thank you for your answer. And what about your repo? Do you have one repo for one country
– Olivier Zoletti
Nov 21 '18 at 16:44
1
no. I have one (self provisioned, operated) git repo. My containers start scripts pull from git. My configs are site specific, the generic form is in git. When I create a container for a stack, I hand-craft (for now) the site specific config form the generic that was pulled. Not optimal, but works ok for the moment. I will tend to look for a 'zeroOps' solution shortly and remove error prone hand-crafting.
– YvesLeBorg
Nov 21 '18 at 17:16