일반적인 패턴입니다. 발행자가 토픽에 메시지를 발행하면 해당 토픽을 구독하고 있는 모든 구
독자가 그 메시지를 즉시 가져갑니다.
pub
/
sub
은 크게 두 가지 시나리오를 제공합니다.
●
발행자와 구독자가 분리되어 있어서 서비스와 함수가 느슨하게 커플링됩니다.
●
이벤트 기반 설계가 가능해서 클라우드 네이티브 애플리케이션에서 보편적인 인기를 얻
고 있는 설계 방법입니다.
크게 보면,
pub
/
sub
은 다음 단계를 따릅니다. [그림
3
-
11
]이 그 내용을 보여줍니다.
1
.
서비스
A
는 토픽에 메시지를 발행합니다.
2
.
메시징 브로커는 해당 토픽을 구독하고 있는 모든 구독자에게 알립니다.
3
.
구독자들이 메시지를 가져갑니다. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.