Creating event-driven microservices: the why, how and what by Andrew Schofield

Any team that has made the jump from building monoliths to building microservices knows the complexities you must overcome to build a system that is functional and maintainable. Building a microservice architecture that is low latency and only communicates using REST APIs is even more tricky, with high latency for requests being a common concern. This talk will explain how you can use events as the backbone of your microservice architecture and build an efficient, event-driven system. It will cover how to get started with designing your microservice architecture and the key requirements any system needs to fulfil. It will also introduce the different patterns you will encounter in event-driven architectures and the advantages and disadvantages of these choices. Finally it will explain why Apache Kafka is a great choice for event-driven microservices.

[assembledstardust]

Definitely one of the better high level overview presentations I've seen on these subject matters. Conceptually I was already familiar with the architecture and I have even put some into practice by rolling our own custom Event Store based on the Event Sourcing architectural pattern (though I admit, probably very poorly) but the speaker has done a great job of combining all of the knowledge and approaches that are our there. Best 40 minutes I've spend on deepening my knowledge and understanding in this area.


Thanks for the upload.

[rajivbhatia]

Most definitely one of the most complete walkthrough of SAGA implementation using event sourcing (and orchestration). Excellent job on combining approaches, patterns, and examples out there.

[johannisdihayco]

Fantastic talk. A very clear discussion of event-driven micro services.

[srikuhere]

brilliant talk, how all the concepts around micro services and event driven arch came together was like an art masterpiece . thank you for posting this talk . Appreciate it .

[Pro_PlayerVedanth]

What an holistic explanation of the Architecture taking a practical problem situation ! Kudos.!

[krumbergify]

A common argument for microservices is that it leads to decoupling between parts and less ”spagetti”. However I fear that overusing publish/subscribe yields the same kind of spagetti, just over a network instead of between functions and classes.

[vivekjacob]

One of the better videos which gives a rationale for event driven architecture

[osamaa.h.altameemi]

That was really slick. Thx a ton. I am shocked by the existing gap between what the industry has and what most of people in Academia are trying to re-invent. IoT Researchers should have the topics in this talk as their starting point and improve up-on. Not re-invent the same wheel 1000 times.

[lifeisbeautiful]

Good one, indeed. Inclusion of real production problem solution using patterns like Not only DB, Sagas, Event sourcing helps to understand real-life problem along with the solution.

[srvmojo]

this was a great presentation !! i wonder how the audience never had any question !!

[Jam-htky]

beautifully done presentation and excellently presented great job

[stepseiventures]

This was awesome and with the British accent, making it exciting. Nice presentation on EDA and microservices

[frustin]

This is a really good explanation of event driven microservices/architecture

[shivchatur]

nice one seen this just today.
will discuss with my team, if this approach can be used in my current project.
thanks Andrew.

[RodyDavis]

This was incredible, I know understand pub/sub

[willl]

I think micro services is really hard to get right, but if you do the benefits are substantial

[nasserabbassi]

just by the way the mentioned link by Andrew on IBM website is not available

[kevinkkirimii]

Is there any event driven video without kafka ?

[kleberpovoacao]

At CQRS slide (36:24 minute) why not use some replication feature from database instead of event backbone ? Not clear for me the benefit using event backbone on this case.

[digisecureagent]

do we need to have event sourcing. + saga at the same time to achieve consistency or event sourcing alone is enough?