From the course: Building Event-Driven Applications In Go

Unlock this course with a free trial

Join today to access over 24,800 courses taught by industry experts.

Implementing message-driven communication patterns: Things you should know

Implementing message-driven communication patterns: Things you should know

From the course: Building Event-Driven Applications In Go

Start my 1-month free trial Buy for my team

Implementing message-driven communication patterns: Things you should know

“

- [Instructor] In the last video, we looked at some interesting concepts and got our hands dirty with a little example. Let's dive in yet further in this video and let's talk a bit more about implementing message-driven communication patterns. Now, when it comes to message-driven architecture or event-driven architecture, as with every other thing in software engineering and indeed life, there are benefits and then there are drawbacks. And I want to spend some time just looking at some of the prominent benefits and drawbacks of this. So what are some benefits of message-driven communication? Firstly, like I've said over and over again in this course, decoupling of components. Decoupling of components is particularly helpful because it leads to, in a sense, fault tolerance. Message-driven communication allows components to be loosely coupled, each component only needs to know how to send and receive messages and they don't exactly need to be in the same application or they don't even…

Contents