Creating two services and connecting them





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







-1















So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.



Service A has two task:




  • Accept HTTP request that carry money information

  • Generate AMQP messages towards "Service B"


Service B has two tasks:




  • Service accepts AMQP messages generated by Service A

  • Service must have account entity stored in database, described by two properties, balance and updatedAt


I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.










share|improve this question





























    -1















    So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.



    Service A has two task:




    • Accept HTTP request that carry money information

    • Generate AMQP messages towards "Service B"


    Service B has two tasks:




    • Service accepts AMQP messages generated by Service A

    • Service must have account entity stored in database, described by two properties, balance and updatedAt


    I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.










    share|improve this question

























      -1












      -1








      -1








      So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.



      Service A has two task:




      • Accept HTTP request that carry money information

      • Generate AMQP messages towards "Service B"


      Service B has two tasks:




      • Service accepts AMQP messages generated by Service A

      • Service must have account entity stored in database, described by two properties, balance and updatedAt


      I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.










      share|improve this question














      So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.



      Service A has two task:




      • Accept HTTP request that carry money information

      • Generate AMQP messages towards "Service B"


      Service B has two tasks:




      • Service accepts AMQP messages generated by Service A

      • Service must have account entity stored in database, described by two properties, balance and updatedAt


      I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.







      php laravel service






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 11:40









      zlatangoralijazlatangoralija

      168




      168
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.



          Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,




          1. Change our way of thought tied to database and joining data across tables to show data

          2. Don't create separate services just for the sake of doing it.

          3. Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus

          4. Micro services should be independently scalable (horizontal scaling)

          5. Think of micro services as something which solves a specific business problem






          share|improve this answer
























            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430210%2fcreating-two-services-and-connecting-them%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.



            Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,




            1. Change our way of thought tied to database and joining data across tables to show data

            2. Don't create separate services just for the sake of doing it.

            3. Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus

            4. Micro services should be independently scalable (horizontal scaling)

            5. Think of micro services as something which solves a specific business problem






            share|improve this answer




























              0














              I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.



              Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,




              1. Change our way of thought tied to database and joining data across tables to show data

              2. Don't create separate services just for the sake of doing it.

              3. Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus

              4. Micro services should be independently scalable (horizontal scaling)

              5. Think of micro services as something which solves a specific business problem






              share|improve this answer


























                0












                0








                0







                I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.



                Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,




                1. Change our way of thought tied to database and joining data across tables to show data

                2. Don't create separate services just for the sake of doing it.

                3. Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus

                4. Micro services should be independently scalable (horizontal scaling)

                5. Think of micro services as something which solves a specific business problem






                share|improve this answer













                I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.



                Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,




                1. Change our way of thought tied to database and joining data across tables to show data

                2. Don't create separate services just for the sake of doing it.

                3. Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus

                4. Micro services should be independently scalable (horizontal scaling)

                5. Think of micro services as something which solves a specific business problem







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 '18 at 14:44









                JeevanJeevan

                1426




                1426
































                    draft saved

                    draft discarded




















































                    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%2f53430210%2fcreating-two-services-and-connecting-them%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

                    鏡平學校

                    ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                    Why https connections are so slow when debugging (stepping over) in Java?