Return to Answer

added 53 characters in body

edited Oct 7, 2024 at 16:05

There are some key distinctions between SNS and SQS:

SNS supports application-to-application (A2A) and application-to-person (A2P) communication, while SQS supports only A2A communication.
SNS is a pub/sub system, while SQS is a queuing system. You'd typically use SNS to send the same message to multiple consumers via topics. In comparison, in most scenarios, each message in an SQS queue is processed by only one consumer. With SQS, messages are delivered through a long polling (pull) mechanism, while SNS uses a push mechanism to immediately deliver messages to subscribed endpoints.
SNS is typically used for applications that need real time notifications, while SQS is more suited for message processing use cases.
SNS does not persist messages - it delivers them to subscribers that are present, and then deletes them. In comparison, SQS can persist messages (from 1 minute to 14 days).

Individually, Amazon SQS and SNS are used for different use cases. You can, however, use them together in some scenarios.

There are some key distinctions between SNS and SQS:

SNS supports A2A and A2P communication, while SQS supports only A2A communication.
SNS is a pub/sub system, while SQS is a queuing system. You'd typically use SNS to send the same message to multiple consumers via topics. In comparison, in most scenarios, each message in an SQS queue is processed by only one consumer. With SQS, messages are delivered through a long polling (pull) mechanism, while SNS uses a push mechanism to immediately deliver messages to subscribed endpoints.
SNS is typically used for applications that need real time notifications, while SQS is more suited for message processing use cases.
SNS does not persist messages - it delivers them to subscribers that are present, and then deletes them. In comparison, SQS can persist messages (from 1 minute to 14 days).

Individually, Amazon SQS and SNS are used for different use cases. You can, however, use them together in some scenarios.

There are some key distinctions between SNS and SQS:

SNS supports application-to-application (A2A) and application-to-person (A2P) communication, while SQS supports only A2A communication.
SNS is a pub/sub system, while SQS is a queuing system. You'd typically use SNS to send the same message to multiple consumers via topics. In comparison, in most scenarios, each message in an SQS queue is processed by only one consumer. With SQS, messages are delivered through a long polling (pull) mechanism, while SNS uses a push mechanism to immediately deliver messages to subscribed endpoints.
SNS is typically used for applications that need real time notifications, while SQS is more suited for message processing use cases.
SNS does not persist messages - it delivers them to subscribers that are present, and then deletes them. In comparison, SQS can persist messages (from 1 minute to 14 days).

Individually, Amazon SQS and SNS are used for different use cases. You can, however, use them together in some scenarios.

answered Dec 22, 2022 at 15:07

There are some key distinctions between SNS and SQS:

SNS supports A2A and A2P communication, while SQS supports only A2A communication.
SNS is a pub/sub system, while SQS is a queuing system. You'd typically use SNS to send the same message to multiple consumers via topics. In comparison, in most scenarios, each message in an SQS queue is processed by only one consumer. With SQS, messages are delivered through a long polling (pull) mechanism, while SNS uses a push mechanism to immediately deliver messages to subscribed endpoints.
SNS is typically used for applications that need real time notifications, while SQS is more suited for message processing use cases.
SNS does not persist messages - it delivers them to subscribers that are present, and then deletes them. In comparison, SQS can persist messages (from 1 minute to 14 days).

Individually, Amazon SQS and SNS are used for different use cases. You can, however, use them together in some scenarios.