SNS와 SQS의 차이?

SNS와 SQS 모두 느슨하게 결합된 마이크로 서비스 애플리케이션을 위해 사용하면 좋다.

근데 두 서비스가 좀 차이가 있다.

SNS는 여러 토픽을 만들고, 그 토픽을 구독한 subscriber에게 message를 전달하는 역할을 한다.

내가 topic에 하나의 메시지를 보내면, 그 topic을 구독한 모든 subscribers에게 메시지가 전달된다.

 

Similarly, Amazon SNS facilitates loosely coupled microservices application architectures by separating the publishing of the message from the receipt or acknowledgement of the message by another service. You begin by creating an SNS topic, which is a channel for messages to be delivered. Then you configure subscribers to that topic. Finally, you publish messages to the subscribers of that topic. This means that you can send one message to a topic and have all the subscribers receive it. These subscribers can be SQS queues, web servers, email addresses, AWS Lambda functions, or several other options. You will learn more about Lambda in the next lesson.

 

ㄴ SNS의 topic의 subscriber는 SQS queue가 될 수 있다!!!

 

Amazon SQS is a message queuing service. Using Amazon SQS, you place messages into a queue, where they remain until another service picks them up from that queue. By using Amazon SQS, you can send, store, and receive messages between software components at any volume. The data contained within a message is called a payload. SQS queues are where messages are placed until they are processed. AWS manages the underlying queue infrastructure so that the message queues scale automatically and reliably.

 

Using Amazon SQS, you can send, store, and receive messages between software components without losing messages or requiring other services to be available. In Amazon SQS, an application sends messages into a queue. A user or service retrieves a message from the queue, processes it, and then deletes it from the queue.

SQS를 사용하면, 소프트웨어 컴포넌트간에 손실 없이 데이터를 주고 받을 수 있다.