How to Unlock the Power of Event-Driven Architecture | Designing Event-Driven Microservices

An Event-Driven Architecture is more than just a set of microservices. Event Streams should represent the central nervous system, providing the bulk of communication between all components in the platform. Unfortunately, many projects stall long before they reach this point.

Teams start by building an initial set of microservices but expanding beyond that to the rest of the system can be a real challenge. Transitioning from Event-Driven Microservices to an Event-Driven Architecture requires treating events like a product. However, the biggest challenge will be convincing the people around you that this is the right solution.

RELATED RESOURCES:

CHAPTERS:
00:00 - Intro
00:29 - What makes a data product successful?
01:08 - How can we meet the needs of the consumer?
01:43 - What makes an event easy to consume?
02:48 - How to ensure events are reliable.
03:32 - How to expand an event-driven system.
05:12 - How to sell your event-driven architecture to the rest of the team.
06:56 - Closing

--

ABOUT CONFLUENT

#microservices #eventdrivenarchitecture #apachekafka #kafka #confluent

[ConfluentDevXTeam]

Wade here. I remember what this was like for me on an early project. We had to expand our Event Driven approach to a wider team. And we absolutely went about it the wrong way. We jumped in with a ton of enthusiasm, talking about all the ways that we were going to change things and how awesome it was going to be. And the people we needed to convince just shut down. They had no interest in what we wanted to hear. It wasn't until I became a consultant that I learned the error of my ways. You can't change the course of a ship instantly. It takes time. You have to build trust first. Once you have people's trust, they will be more open to new ideas. But if you try to throw new ideas at them without that trust, they are going to defend their territory. I blamed it on everyone else for not being open to new ideas. But the reality is that I was to blame for not being empathetic to their needs.

[respergu]

This quote really hit home : We can measure the success of our microservices, by the numbers of consumers that subscribe to its events. Just emiting events is not enough, having useful information to be shared and enriching it are indeed something we need to think about.

[Ultramini]

Thank you, that was a great journey through the topic and you were a really enjoyable host.

[AdamSouquieres]

As usual, I really feel that you manage to put some structure and words on some of my practices.
Must see video.

[kfliden]

Great video! One thing I'm struggling with a bit is in a case where one provides a public rest API with a synchronous calls, will that hide a event-driven architecture that's backing it, where one call to the API kicks off an event flow which has to complete the and terminate at a consumer to be returned by the original API request?

[ghoshsuman]

Please explain how the event enrichments is happening in event driven microservices