► LEARN MORE: [ Ссылка ]
Communication between microservices can be broadly categorized as either point-to-point or publish/subscribe. Point-to-point is often used synchronously, while publish/subscribe tends to be asynchronous. Each of these techniques can have a place in a modern microservices platform, but it is important to understand the role each one plays so that they can be used effectively.
Check out the Designing Event-Driven Microservices course on Confluent Developer for more details: [ Ссылка ]
RELATED RESOURCES
► Publish-Subscribe - Intro to Pub-Sub Messaging: [ Ссылка ]
► Microservices—An Introduction: [ Ссылка ]
► Event-Driven Microservices Architecture: [ Ссылка ]
► Migrate from Monoliths to Event-Driven Microservices: [ Ссылка ]
► Microservices course playlist: [ Ссылка ]
► Get Started on Confluent Developer: [ Ссылка ]
CHAPTERS
00:00 - Intro
00:25 - Real World Communication
01:28 - Point-to-Point Communication
01:53 - Point-to-Point Advantages
02:34 - Point-to-Point Disadvantages
03:51 - Publish/Subscribe Communication
04:28 - Publish/Subscribe Advantages
05:21 - Publish/Subscribe Disadvantages
06:17 - Closing
--
ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.
#microservices #apachekafka #kafka #confluent
