AWS SNS Queing Behaviour












0















We have a logging mechanism through which we broadcast exception logs using Amazon Simple Notification Service.



On working on Amazon Simple Notification Service I figured out that Amazon Simple Notification Service queuing notification(s) which have to published.
How can I avoid this behavior?










share|improve this question





























    0















    We have a logging mechanism through which we broadcast exception logs using Amazon Simple Notification Service.



    On working on Amazon Simple Notification Service I figured out that Amazon Simple Notification Service queuing notification(s) which have to published.
    How can I avoid this behavior?










    share|improve this question



























      0












      0








      0








      We have a logging mechanism through which we broadcast exception logs using Amazon Simple Notification Service.



      On working on Amazon Simple Notification Service I figured out that Amazon Simple Notification Service queuing notification(s) which have to published.
      How can I avoid this behavior?










      share|improve this question
















      We have a logging mechanism through which we broadcast exception logs using Amazon Simple Notification Service.



      On working on Amazon Simple Notification Service I figured out that Amazon Simple Notification Service queuing notification(s) which have to published.
      How can I avoid this behavior?







      amazon-web-services amazon-sns






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 19 '18 at 14:56









      mmvsbg

      2,122153857




      2,122153857










      asked Nov 19 '18 at 13:03









      Nitin ParasharNitin Parashar

      7810




      7810
























          1 Answer
          1






          active

          oldest

          votes


















          0














          A little more details would be needed on the behaviour you're seeing.
          How and where are you measuring this behaviour, on the client Publishing the messages to SNS or on the destination endpoints receiving the notifications?



          What is the issue you are seeing? If it is ordering, ordering is not guaranteed when using SNS:
          https://aws.amazon.com/sns/faqs/




          The Amazon SNS service will attempt to deliver messages from the
          publisher in the order they were published into the topic. However,
          network issues could potentially result in out-of-order messages at
          the subscriber end.







          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%2f53375278%2faws-sns-queing-behaviour%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














            A little more details would be needed on the behaviour you're seeing.
            How and where are you measuring this behaviour, on the client Publishing the messages to SNS or on the destination endpoints receiving the notifications?



            What is the issue you are seeing? If it is ordering, ordering is not guaranteed when using SNS:
            https://aws.amazon.com/sns/faqs/




            The Amazon SNS service will attempt to deliver messages from the
            publisher in the order they were published into the topic. However,
            network issues could potentially result in out-of-order messages at
            the subscriber end.







            share|improve this answer




























              0














              A little more details would be needed on the behaviour you're seeing.
              How and where are you measuring this behaviour, on the client Publishing the messages to SNS or on the destination endpoints receiving the notifications?



              What is the issue you are seeing? If it is ordering, ordering is not guaranteed when using SNS:
              https://aws.amazon.com/sns/faqs/




              The Amazon SNS service will attempt to deliver messages from the
              publisher in the order they were published into the topic. However,
              network issues could potentially result in out-of-order messages at
              the subscriber end.







              share|improve this answer


























                0












                0








                0







                A little more details would be needed on the behaviour you're seeing.
                How and where are you measuring this behaviour, on the client Publishing the messages to SNS or on the destination endpoints receiving the notifications?



                What is the issue you are seeing? If it is ordering, ordering is not guaranteed when using SNS:
                https://aws.amazon.com/sns/faqs/




                The Amazon SNS service will attempt to deliver messages from the
                publisher in the order they were published into the topic. However,
                network issues could potentially result in out-of-order messages at
                the subscriber end.







                share|improve this answer













                A little more details would be needed on the behaviour you're seeing.
                How and where are you measuring this behaviour, on the client Publishing the messages to SNS or on the destination endpoints receiving the notifications?



                What is the issue you are seeing? If it is ordering, ordering is not guaranteed when using SNS:
                https://aws.amazon.com/sns/faqs/




                The Amazon SNS service will attempt to deliver messages from the
                publisher in the order they were published into the topic. However,
                network issues could potentially result in out-of-order messages at
                the subscriber end.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 4 '18 at 14:35









                Alexandru TodicescuAlexandru Todicescu

                11




                11






























                    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%2f53375278%2faws-sns-queing-behaviour%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

                    Guess what letter conforming each word

                    Port of Spain

                    Run scheduled task as local user group (not BUILTIN)