Engineering the Future of Software
29–31 Oct 2018: Tutorials & Conference
31 Oct–1 Nov 2018: Training
London, UK

Async in Microservices and Its Three Forms: Understanding the Patterns

Irakli Nadareishvili (Capital One)

Who is this presentation for?

Software engineers, architects and technical product managers

Prerequisite knowledge

Experience developing complex systems, basic understanding of messaging systems, microservices principles and async programming

What you'll learn

We often find significant confusion among developers and architects when they implement cloud-native applications and have to design asynchronous flows. These are relatively new aspects of software design and various patterns are commonly confused. We see teams implementing messaging infrastructure for Event Sourcing or confusing Reactive patterns in Akka with "microservice architecture". This talk helps remove the confusion and provide authoritative guideline to assist in better implementations of cloud-native, distributed and microservices applications.

Description

We will discuss three major async forms that
are most relevant in the space: Event Sourcing, Async
Command Processing (Reactiveness), and Data Streams.

We will define each one of the patterns, explain relevant
use-cases, using examples from FinTech context, and discuss
differences in implementation.

The examples and guidelines are derived from presenter’s extensive experience working with many exciting organizations, during his API Academy tenure and most recently: leading microservices transformation at Capital One. We also compare the experience to the experience in the rest of the industry, deriving insights from take-aways from companies such as Netflix, Soundcloud, Amazon and other early microservices adopters.

Video Sample: https://www.youtube.com/watch?v=x8bWBOwstaw
Full List of talks, writing: http://www.freshblurbs.com/articles/speaking.html


Audience

The ideal audience are developers and architects adopting cloud-native design practices, such as: microservice architecture, and finding themselves in various pitfalls when dealing with the new design paradigms that are
less discussed in the existing literature or for which often there
is conflicting and confusing information on the web.

The examples and guidelines, in this talk, are derived from presenter’s extensive experience working with many exciting organizations, during his API Academy tenure and most recently: leading microservices transformation at Capital One.

— Benefits

We often find significant confusion among developers and architects
when they implement cloud-native applications and have to
design asynchronous flows. These are relatively new aspects of
software design and various patterns are commonly confused. We
see teams implementing messaging infrastructure for Event Sourcing
or confusing Reactive patterns in Akka with “microservice architecture”.
This talk helps remove the confusion and provide
authoritative guideline to assist in better implementations
of cloud-native, distributed and microservices applications.

Photo of Irakli Nadareishvili

Irakli Nadareishvili

Capital One

Irakli Nadareishvili is currently leading microservices transformation efforts as the Senior Director of technology at Capital One. Irakli is a co-author of Microservice Architecture (O’Reilly 2016), and was formerly co-founder and CTO of ReferWell, a NY-based health technology startup. In the past he has also held technology leadership roles at CA Technologies and NPR. You can follow Irakli on Twitter at @inadarei

Leave a Comment or Question

Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?

Join the conversation here (requires login)