Sign in to confirm you’re not a bot
This helps protect our community. Learn more

How to (not) build a distributed monolith - orchestrate using Netflix Conductor

Microsoft Reactor
115K subscribers
<__slot-el>
<__slot-el>
651 views Streamed 2 years ago
You build your applications on microservices architecture. You like the fact that you can follow the single responsibility principle and build services that can be independently scaled and reasoned about. A typical business application requires coordination across multiple microservices. This creates a dilemma, where do you put the coordination logic: Is this a new service, do services publish messages to a pub/sub system like Kafka or Azure Service Bus? If so, you are halfway there! In this session, we will learn about the pitfalls of invariably building a distributed monolith, challenges that comes with it and how we can leverage evening systems with an orchestrator like Netflix Conductor to make a distributed stateful microservices based application that provides agility that you desire with operational visibility, control and more importantly correctness of the distributed system. [eventID:18799] ...more
...more
These chapters are auto-generated

Reactor monolith - orchestrate using

0:00

Is this your application architecture?

2:10

Anatomy of a distributed application

4:40

Distributed applications with Event Driven Architecture

6:36

Event Driven Architecture with Pub/Sub

8:10

Distributed Monoliths & Operational Complexity

16:33

Avoiding Distributed Monolith

21:24

Case for a well-formed Orchestrator

27:46

Building Distributed Applications w/ Conductor (2/2)

32:11

(do not) Build a Distributed Monolith - with Conductor

39:38

Application Development with Conductor

42:28

Long Running Workflows, Rate Limits, Retries

46:13

Inside the architecture of Conductor

48:00
How to (not) build a distributed monolith - orchestrate using Netflix Conductor
You build your applications on microservices architecture. You like the fact that you can follow the single responsibility principle and build services that can be independently scaled and reasoned about. A typical business application requires coordination across multiple microservices. This creates a dilemma, where do you put the coordination logic: Is this a new service, do services publish messages to a pub/sub system like Kafka or Azure Service Bus? If so, you are halfway there! In this session, we will learn about the pitfalls of invariably building a distributed monolith, challenges that comes with it and how we can leverage evening systems with an orchestrator like Netflix Conductor to make a distributed stateful microservices based application that provides agility that you desire with operational visibility, control and more importantly correctness of the distributed system. [eventID:18799]

Follow along using the transcript.

Microsoft Reactor

115K subscribers
Live chat replay is not available for this video.