Cons of using Ajax for Autocomplete search operation?












0















I am working on E-commerce application & I want to implement a google like search functionality with autocomplete and spelling correction.




  1. What are the cons if I implement this using Ajax, I mean in terms of performance and the load on the server since its E-commerce website.

  2. Are there any alternative solutions?










share|improve this question





























    0















    I am working on E-commerce application & I want to implement a google like search functionality with autocomplete and spelling correction.




    1. What are the cons if I implement this using Ajax, I mean in terms of performance and the load on the server since its E-commerce website.

    2. Are there any alternative solutions?










    share|improve this question



























      0












      0








      0








      I am working on E-commerce application & I want to implement a google like search functionality with autocomplete and spelling correction.




      1. What are the cons if I implement this using Ajax, I mean in terms of performance and the load on the server since its E-commerce website.

      2. Are there any alternative solutions?










      share|improve this question
















      I am working on E-commerce application & I want to implement a google like search functionality with autocomplete and spelling correction.




      1. What are the cons if I implement this using Ajax, I mean in terms of performance and the load on the server since its E-commerce website.

      2. Are there any alternative solutions?







      javascript node.js ajax reactjs e-commerce






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 13 '18 at 20:58







      Haha

















      asked Nov 13 '18 at 20:09









      HahaHaha

      11




      11
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I would say that you should try and use observables before you hit the ajax. Observables from the rxjs library will let you plan how to use your autocomplete so that you aren't hitting the server unnecessarily. One example is a debounce Time so that you don't trigger a new search every time a user types, but instead wait a couple of seconds for the user to finish typing. This will also allow you to avoid hitting the server when a user has a typo and uses backspace.






          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%2f53288736%2fcons-of-using-ajax-for-autocomplete-search-operation%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 would say that you should try and use observables before you hit the ajax. Observables from the rxjs library will let you plan how to use your autocomplete so that you aren't hitting the server unnecessarily. One example is a debounce Time so that you don't trigger a new search every time a user types, but instead wait a couple of seconds for the user to finish typing. This will also allow you to avoid hitting the server when a user has a typo and uses backspace.






            share|improve this answer




























              0














              I would say that you should try and use observables before you hit the ajax. Observables from the rxjs library will let you plan how to use your autocomplete so that you aren't hitting the server unnecessarily. One example is a debounce Time so that you don't trigger a new search every time a user types, but instead wait a couple of seconds for the user to finish typing. This will also allow you to avoid hitting the server when a user has a typo and uses backspace.






              share|improve this answer


























                0












                0








                0







                I would say that you should try and use observables before you hit the ajax. Observables from the rxjs library will let you plan how to use your autocomplete so that you aren't hitting the server unnecessarily. One example is a debounce Time so that you don't trigger a new search every time a user types, but instead wait a couple of seconds for the user to finish typing. This will also allow you to avoid hitting the server when a user has a typo and uses backspace.






                share|improve this answer













                I would say that you should try and use observables before you hit the ajax. Observables from the rxjs library will let you plan how to use your autocomplete so that you aren't hitting the server unnecessarily. One example is a debounce Time so that you don't trigger a new search every time a user types, but instead wait a couple of seconds for the user to finish typing. This will also allow you to avoid hitting the server when a user has a typo and uses backspace.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 20:12









                Pari BakerPari Baker

                223113




                223113






























                    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%2f53288736%2fcons-of-using-ajax-for-autocomplete-search-operation%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

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python