Monolithic + MicroServices Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Data science time! April 2019 and salary with experience The Ask Question Wizard is Live!How does data denormalization work with the Microservice Pattern?Cross-Microservice Authorization and AuthenticationMicroservices vs Monolithic ArchitectureTransferring from a monolithic application to a micro service one - approachHow to share the web API controllers with microserviceAuthorization of actions across microservicesMigrating multi-module project to microservices?Microservice arquitectureAsync response from API Gateway in microservicesHow to manage multiple staging environment in between transition from monolithic to microservice architecture

Using audio cues to encourage good posture

SF book about people trapped in a series of worlds they imagine

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

What is "gratricide"?

Chinese Seal on silk painting - what does it mean?

How to tell that you are a giant?

Most bit efficient text communication method?

What is the appropriate index architecture when forced to implement IsDeleted (soft deletes)?

Do I really need to have a message in a novel to appeal to readers?

Selecting user stories during sprint planning

How does the secondary effect of the Heat Metal spell interact with a creature resistant/immune to fire damage?

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Hangman Game with C++

Is it fair for a professor to grade us on the possession of past papers?

How to play a character with a disability or mental disorder without being offensive?

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

How do living politicians protect their readily obtainable signatures from misuse?

Trademark violation for app?

Project Euler #1 in C++

Disembodied hand growing fangs

Is a ledger board required if the side of my house is wood?

How do I find out the mythology and history of my Fortress?

What is the difference between globalisation and imperialism?

Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?



Monolithic + MicroServices



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Data science time! April 2019 and salary with experience
The Ask Question Wizard is Live!How does data denormalization work with the Microservice Pattern?Cross-Microservice Authorization and AuthenticationMicroservices vs Monolithic ArchitectureTransferring from a monolithic application to a micro service one - approachHow to share the web API controllers with microserviceAuthorization of actions across microservicesMigrating multi-module project to microservices?Microservice arquitectureAsync response from API Gateway in microservicesHow to manage multiple staging environment in between transition from monolithic to microservice architecture



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








6















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.










share|improve this question







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
    10 hours ago











  • 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
    8 hours ago











  • Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

    – Nathan Hughes
    7 hours ago

















6















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.










share|improve this question







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
    10 hours ago











  • 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
    8 hours ago











  • Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

    – Nathan Hughes
    7 hours ago













6












6








6


1






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.










share|improve this question







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






share|improve this question







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.











share|improve this question







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.









share|improve this question




share|improve this question






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 10 hours ago









Nikola TordoofNikola Tordoof

333




333




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
    10 hours ago











  • 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
    8 hours ago











  • Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

    – Nathan Hughes
    7 hours ago

















  • Do you mean build a monolith and cram it into the cloud as-is without any re-design?

    – Nathan Hughes
    10 hours ago











  • 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
    8 hours ago











  • Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

    – Nathan Hughes
    7 hours ago
















Do you mean build a monolith and cram it into the cloud as-is without any re-design?

– Nathan Hughes
10 hours ago





Do you mean build a monolith and cram it into the cloud as-is without any re-design?

– Nathan Hughes
10 hours ago













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
8 hours ago





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
8 hours ago













Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

– Nathan Hughes
7 hours ago





Microservices are more work and don’t share much if anything in common with monolith design. So you’d be writing the application twice, where the second way was much harder.

– Nathan Hughes
7 hours ago












4 Answers
4






active

oldest

votes


















3














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 correct answer 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/#/






share|improve this answer




















  • 3





    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
    37 mins ago



















4














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.






share|improve this answer






























    4














    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.






    share|improve this answer








    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 agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

      – Yanaz Hyrovakas
      17 mins ago


















    3














    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.






    share|improve this answer


















    • 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
      1 hour ago






    • 1





      yes absolutely.. that is 2 minute job

      – Deepak
      1 hour ago







    • 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
      54 mins ago






    • 2





      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.

      – vaquar khan
      35 mins ago







    • 1





      @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

      – Deepak
      11 mins ago











    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.









    draft saved

    draft discarded


















    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









    3














    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 correct answer 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/#/






    share|improve this answer




















    • 3





      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
      37 mins ago
















    3














    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 correct answer 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/#/






    share|improve this answer




















    • 3





      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
      37 mins ago














    3












    3








    3







    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 correct answer 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/#/






    share|improve this answer















    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 correct answer 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/#/







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 33 mins ago

























    answered 40 mins ago









    vaquar khanvaquar khan

    3,64212143




    3,64212143







    • 3





      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
      37 mins ago













    • 3





      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
      37 mins ago








    3




    3





    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
    37 mins ago






    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
    37 mins ago














    4














    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.






    share|improve this answer



























      4














      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.






      share|improve this answer

























        4












        4








        4







        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.






        share|improve this answer













        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 42 mins ago









        Hank MoodyHank Moody

        565




        565





















            4














            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.






            share|improve this answer








            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 agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

              – Yanaz Hyrovakas
              17 mins ago















            4














            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.






            share|improve this answer








            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 agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

              – Yanaz Hyrovakas
              17 mins ago













            4












            4








            4







            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.






            share|improve this answer








            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.







            share|improve this answer








            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.









            share|improve this answer



            share|improve this answer






            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 34 mins ago









            Ekaterina MakesimovaEkaterina Makesimova

            413




            413




            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.












            • I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

              – Yanaz Hyrovakas
              17 mins ago

















            • I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

              – Yanaz Hyrovakas
              17 mins ago
















            I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

            – Yanaz Hyrovakas
            17 mins ago





            I agree with Ekatarina, its very wise to build micro services from the beginning to avoid rebuilding everything from scratch later.

            – Yanaz Hyrovakas
            17 mins ago











            3














            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.






            share|improve this answer


















            • 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
              1 hour ago






            • 1





              yes absolutely.. that is 2 minute job

              – Deepak
              1 hour ago







            • 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
              54 mins ago






            • 2





              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.

              – vaquar khan
              35 mins ago







            • 1





              @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

              – Deepak
              11 mins ago















            3














            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.






            share|improve this answer


















            • 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
              1 hour ago






            • 1





              yes absolutely.. that is 2 minute job

              – Deepak
              1 hour ago







            • 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
              54 mins ago






            • 2





              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.

              – vaquar khan
              35 mins ago







            • 1





              @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

              – Deepak
              11 mins ago













            3












            3








            3







            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.






            share|improve this answer













            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.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 1 hour ago









            DeepakDeepak

            5,53383574




            5,53383574







            • 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
              1 hour ago






            • 1





              yes absolutely.. that is 2 minute job

              – Deepak
              1 hour ago







            • 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
              54 mins ago






            • 2





              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.

              – vaquar khan
              35 mins ago







            • 1





              @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

              – Deepak
              11 mins ago












            • 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
              1 hour ago






            • 1





              yes absolutely.. that is 2 minute job

              – Deepak
              1 hour ago







            • 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
              54 mins ago






            • 2





              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.

              – vaquar khan
              35 mins ago







            • 1





              @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

              – Deepak
              11 mins ago







            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
            1 hour ago





            "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
            1 hour ago




            1




            1





            yes absolutely.. that is 2 minute job

            – Deepak
            1 hour ago






            yes absolutely.. that is 2 minute job

            – Deepak
            1 hour ago





            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
            54 mins ago





            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
            54 mins ago




            2




            2





            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.

            – vaquar khan
            35 mins ago






            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.

            – vaquar khan
            35 mins ago





            1




            1





            @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

            – Deepak
            11 mins ago





            @vaquarkhan it depends on case to case basis.. if u deploy both micro-service on same VM; then cost is same w.r.t. infrastrature.. why u disagree ?

            – Deepak
            11 mins ago










            Nikola Tordoof is a new contributor. Be nice, and check out our Code of Conduct.









            draft saved

            draft discarded


















            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

            How to solve knockout JS error in Magento 2 Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2

            Nissan Patrol Зміст Перше покоління — 4W60 (1951-1960) | Друге покоління — 60 series (1960-1980) | Третє покоління (1980–2002) | Четверте покоління — Y60 (1987–1998) | П'яте покоління — Y61 (1997–2013) | Шосте покоління — Y62 (2010- ) | Посилання | Зноски | Навігаційне менюОфіційний український сайтТест-драйв Nissan Patrol 2010 7-го поколінняNissan PatrolКак мы тестировали Nissan Patrol 2016рвиправивши або дописавши її