Reducing Microservice Complexity with Kafka and Reactive Streams - by Jim Riecken

Abstract:
Transitioning from a monolithic application to a set of microservices can help increase performance and scalability, but it can also drastically increase complexity. Layers of inter-service network calls for add latency and an increasing risk of failure where previously only local function calls existed. In this talk, I'll speak about how to tame this complexity using Apache Kafka and Reactive Streams to:
- Extract non-critical processing from the critical path of your application to reduce request latency
- Provide back-pressure to handle both slow and fast producers/consumers
- Maintain high availability, high performance, and reliable messaging
- Evolve message payloads while maintaining backwards and forwards compatibility.

[jeffsmith]

Great talk. Thx!
Curious if there are any metrics for detecting when microservice architectures are becoming too tightly coupled?

[broilogabriel]

Really nice talk, direct and with simple examples! Thanks

[matib]

Top notch content, thank you very much for sharing knowledge and this presentation!

[calvinfernandes]

Great talk :-)
You explained Kafka really well

[skylvid]

Seems a bit confused. Monorepo != monolith. With monorepo you can have a ton of independent services but still get atomic changes ... also the builds can be as independent as they need to be ...

[juergenheymann]

Terrible sound quality. Can you regenerate and repost?