Monolithic + MicroServices
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Right now I need to know exactly how can I instantly deploy a micro service based backend when needed? I can manage all the integration of technologies by myself but when it comes to hosting on AWS its just impossible for me to get those many instances and it is just impossible to afford right now.
Im contemplating on the idea of starting with a monolithic backend while having the possibility of deploying micro services backend instantly when the business kicks off.
But Im not sure how to achieve this idea if ever it is possible.
Is it possible or am I wrong?
Please help, thanks.
microservices backend
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Right now I need to know exactly how can I instantly deploy a micro service based backend when needed? I can manage all the integration of technologies by myself but when it comes to hosting on AWS its just impossible for me to get those many instances and it is just impossible to afford right now.
Im contemplating on the idea of starting with a monolithic backend while having the possibility of deploying micro services backend instantly when the business kicks off.
But Im not sure how to achieve this idea if ever it is possible.
Is it possible or am I wrong?
Please help, thanks.
microservices backend
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34
add a comment |
Right now I need to know exactly how can I instantly deploy a micro service based backend when needed? I can manage all the integration of technologies by myself but when it comes to hosting on AWS its just impossible for me to get those many instances and it is just impossible to afford right now.
Im contemplating on the idea of starting with a monolithic backend while having the possibility of deploying micro services backend instantly when the business kicks off.
But Im not sure how to achieve this idea if ever it is possible.
Is it possible or am I wrong?
Please help, thanks.
microservices backend
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Right now I need to know exactly how can I instantly deploy a micro service based backend when needed? I can manage all the integration of technologies by myself but when it comes to hosting on AWS its just impossible for me to get those many instances and it is just impossible to afford right now.
Im contemplating on the idea of starting with a monolithic backend while having the possibility of deploying micro services backend instantly when the business kicks off.
But Im not sure how to achieve this idea if ever it is possible.
Is it possible or am I wrong?
Please help, thanks.
microservices backend
microservices backend
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
asked Apr 18 at 20:17
Nikola TordoofNikola Tordoof
514
514
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nikola Tordoof is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34
add a comment |
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34
add a comment |
4 Answers
4
active
oldest
votes
This is common issue if planing to use Aws EBS, I had same issue and solved using following approch
1) Think design as monolithic and then decide further into bounded context and each bounded context will be a microservicea.
2) Now design your database and try to keep.each microservice db into separate schema.
3) Now in maven module create parent child module .
4) In parents module keep your spring boot main method, swagger,and common module like security etc
5) Disable spring boot nature in child module .
6) Add all child module microservice into parent module and maven build install.
7) Deploy on AWS EBS .
8 ) Expose all microservice using Aws Api getway.
Benefits: in future whenever you will be able to support infrastructure cost just move module and db schema and no other changes required.
Disagreed with statement that "wrong perception that deploying monolithic is cheaper than micro-services" plz check Aws cost estimations monolythic is cheaper then microservice ,microservice need polygot persistence and independent hosting.
https://aws.amazon.com/premiumsupport/knowledge-center/estimating-aws-resource-costs/
https://calculator.aws/#/
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
add a comment |
Firstly, it is a wrong perception that deploying monolithic is cheaper than micro-services w.r.t. infrastructure..If you are sure you want to go micro-services way; then its better to build it now..
You can build multiple micro-services and deploy on same virtual machine.
Also, these days you have many light weight technologies ( lighter than spring boot ) which has lesser memory footprint, faster start up time like micronaut.
Also, until and unless you are running at scale of Amazon... it is a wrong perception that monolithic cannot scale..Even monolithic can handle quite good number of requests.
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
|
show 14 more comments
I feel like building micro services from day 1 is the best approach these days, no one knows which of your services goes viral. You can not afford a blackout when everyone wants to connect to your services.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
add a comment |
It is very possible to build multiple micro-services and run on the same server / vps and when your project / service goes viral over-night you can always dedicate a separate instance / server for each service easily.
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
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
});
}
});
Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.
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%2f55753184%2fmonolithic-microservices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is common issue if planing to use Aws EBS, I had same issue and solved using following approch
1) Think design as monolithic and then decide further into bounded context and each bounded context will be a microservicea.
2) Now design your database and try to keep.each microservice db into separate schema.
3) Now in maven module create parent child module .
4) In parents module keep your spring boot main method, swagger,and common module like security etc
5) Disable spring boot nature in child module .
6) Add all child module microservice into parent module and maven build install.
7) Deploy on AWS EBS .
8 ) Expose all microservice using Aws Api getway.
Benefits: in future whenever you will be able to support infrastructure cost just move module and db schema and no other changes required.
Disagreed with statement that "wrong perception that deploying monolithic is cheaper than micro-services" plz check Aws cost estimations monolythic is cheaper then microservice ,microservice need polygot persistence and independent hosting.
https://aws.amazon.com/premiumsupport/knowledge-center/estimating-aws-resource-costs/
https://calculator.aws/#/
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
add a comment |
This is common issue if planing to use Aws EBS, I had same issue and solved using following approch
1) Think design as monolithic and then decide further into bounded context and each bounded context will be a microservicea.
2) Now design your database and try to keep.each microservice db into separate schema.
3) Now in maven module create parent child module .
4) In parents module keep your spring boot main method, swagger,and common module like security etc
5) Disable spring boot nature in child module .
6) Add all child module microservice into parent module and maven build install.
7) Deploy on AWS EBS .
8 ) Expose all microservice using Aws Api getway.
Benefits: in future whenever you will be able to support infrastructure cost just move module and db schema and no other changes required.
Disagreed with statement that "wrong perception that deploying monolithic is cheaper than micro-services" plz check Aws cost estimations monolythic is cheaper then microservice ,microservice need polygot persistence and independent hosting.
https://aws.amazon.com/premiumsupport/knowledge-center/estimating-aws-resource-costs/
https://calculator.aws/#/
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
add a comment |
This is common issue if planing to use Aws EBS, I had same issue and solved using following approch
1) Think design as monolithic and then decide further into bounded context and each bounded context will be a microservicea.
2) Now design your database and try to keep.each microservice db into separate schema.
3) Now in maven module create parent child module .
4) In parents module keep your spring boot main method, swagger,and common module like security etc
5) Disable spring boot nature in child module .
6) Add all child module microservice into parent module and maven build install.
7) Deploy on AWS EBS .
8 ) Expose all microservice using Aws Api getway.
Benefits: in future whenever you will be able to support infrastructure cost just move module and db schema and no other changes required.
Disagreed with statement that "wrong perception that deploying monolithic is cheaper than micro-services" plz check Aws cost estimations monolythic is cheaper then microservice ,microservice need polygot persistence and independent hosting.
https://aws.amazon.com/premiumsupport/knowledge-center/estimating-aws-resource-costs/
https://calculator.aws/#/
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
This is common issue if planing to use Aws EBS, I had same issue and solved using following approch
1) Think design as monolithic and then decide further into bounded context and each bounded context will be a microservicea.
2) Now design your database and try to keep.each microservice db into separate schema.
3) Now in maven module create parent child module .
4) In parents module keep your spring boot main method, swagger,and common module like security etc
5) Disable spring boot nature in child module .
6) Add all child module microservice into parent module and maven build install.
7) Deploy on AWS EBS .
8 ) Expose all microservice using Aws Api getway.
Benefits: in future whenever you will be able to support infrastructure cost just move module and db schema and no other changes required.
Disagreed with statement that "wrong perception that deploying monolithic is cheaper than micro-services" plz check Aws cost estimations monolythic is cheaper then microservice ,microservice need polygot persistence and independent hosting.
https://aws.amazon.com/premiumsupport/knowledge-center/estimating-aws-resource-costs/
https://calculator.aws/#/
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
edited Apr 19 at 14:46
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
answered Apr 19 at 6:12
vaquar khanvaquar khan
3,73012243
3,73012243
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
add a comment |
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
4
4
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
I dont know anything about "spring boot". Im going to use GoLang, Node.js, Cassandra, Mysql, Redis, HAProxy, NGinX. Can you please elaborate on that?
– Nikola Tordoof
Apr 19 at 6:15
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
add a comment |
Firstly, it is a wrong perception that deploying monolithic is cheaper than micro-services w.r.t. infrastructure..If you are sure you want to go micro-services way; then its better to build it now..
You can build multiple micro-services and deploy on same virtual machine.
Also, these days you have many light weight technologies ( lighter than spring boot ) which has lesser memory footprint, faster start up time like micronaut.
Also, until and unless you are running at scale of Amazon... it is a wrong perception that monolithic cannot scale..Even monolithic can handle quite good number of requests.
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
|
show 14 more comments
Firstly, it is a wrong perception that deploying monolithic is cheaper than micro-services w.r.t. infrastructure..If you are sure you want to go micro-services way; then its better to build it now..
You can build multiple micro-services and deploy on same virtual machine.
Also, these days you have many light weight technologies ( lighter than spring boot ) which has lesser memory footprint, faster start up time like micronaut.
Also, until and unless you are running at scale of Amazon... it is a wrong perception that monolithic cannot scale..Even monolithic can handle quite good number of requests.
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
|
show 14 more comments
Firstly, it is a wrong perception that deploying monolithic is cheaper than micro-services w.r.t. infrastructure..If you are sure you want to go micro-services way; then its better to build it now..
You can build multiple micro-services and deploy on same virtual machine.
Also, these days you have many light weight technologies ( lighter than spring boot ) which has lesser memory footprint, faster start up time like micronaut.
Also, until and unless you are running at scale of Amazon... it is a wrong perception that monolithic cannot scale..Even monolithic can handle quite good number of requests.
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
Firstly, it is a wrong perception that deploying monolithic is cheaper than micro-services w.r.t. infrastructure..If you are sure you want to go micro-services way; then its better to build it now..
You can build multiple micro-services and deploy on same virtual machine.
Also, these days you have many light weight technologies ( lighter than spring boot ) which has lesser memory footprint, faster start up time like micronaut.
Also, until and unless you are running at scale of Amazon... it is a wrong perception that monolithic cannot scale..Even monolithic can handle quite good number of requests.
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
answered Apr 19 at 4:57
DeepakDeepak
5,58183574
5,58183574
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
|
show 14 more comments
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
2
2
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
"You can build multiple micro-services and deploy on same virtual machine." -------- So using this approach I can dedicate a virtual machine for each micro service easily when I get too much traffic later?
– Nikola Tordoof
Apr 19 at 5:43
2
2
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
Thanks a lot for helping me clear my confusion and kill my headache which was there from 20+ days. Now I know what to do.
– Nikola Tordoof
Apr 19 at 5:58
4
4
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
@Deepak "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:44
5
5
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
@vaquarkhan "but still with micro-services u will have to run multiple JVM which MIGHT need a bigger machine.." ----- So the conclusion is to get multiple instances for each microservice or forget the project as price for both approaches is almost the same?
– Nikola Tordoof
Apr 19 at 9:45
4
4
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
@vaquarkhan What you would have done if you were in my place?
– Nikola Tordoof
Apr 19 at 10:25
|
show 14 more comments
I feel like building micro services from day 1 is the best approach these days, no one knows which of your services goes viral. You can not afford a blackout when everyone wants to connect to your services.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
add a comment |
I feel like building micro services from day 1 is the best approach these days, no one knows which of your services goes viral. You can not afford a blackout when everyone wants to connect to your services.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
add a comment |
I feel like building micro services from day 1 is the best approach these days, no one knows which of your services goes viral. You can not afford a blackout when everyone wants to connect to your services.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I feel like building micro services from day 1 is the best approach these days, no one knows which of your services goes viral. You can not afford a blackout when everyone wants to connect to your services.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
answered Apr 19 at 6:18
Ekaterina MakesimovaEkaterina Makesimova
513
513
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Ekaterina Makesimova is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
add a comment |
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
1
1
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.
– Yanaz Hyrovakas
Apr 19 at 6:35
add a comment |
It is very possible to build multiple micro-services and run on the same server / vps and when your project / service goes viral over-night you can always dedicate a separate instance / server for each service easily.
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
add a comment |
It is very possible to build multiple micro-services and run on the same server / vps and when your project / service goes viral over-night you can always dedicate a separate instance / server for each service easily.
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
add a comment |
It is very possible to build multiple micro-services and run on the same server / vps and when your project / service goes viral over-night you can always dedicate a separate instance / server for each service easily.
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
It is very possible to build multiple micro-services and run on the same server / vps and when your project / service goes viral over-night you can always dedicate a separate instance / server for each service easily.
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
answered Apr 19 at 6:10
Hank MoodyHank Moody
566
566
add a comment |
add a comment |
Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.
Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.
Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.
Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.
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%2f55753184%2fmonolithic-microservices%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
Do you mean build a monolith and cram it into the cloud as-is without any re-design?
– Nathan Hughes
Apr 18 at 20:48
No, maybe like 2 separate projects achieving same goal but monolith project will be used first then when there is a good success I can switch to micro services. I dont know whether this is possible or makes any sense.
– Nikola Tordoof
Apr 18 at 22:34