All videos
Opera view

Lessons learnt from going reactive with Reactor

October 9, 2019

Apache James is a mail server with a long history. A huge part of its work is to deal with Inputs Outputs (IMAP, SMTP, Jmap, Cassandra, RabbitMQ, AWS S3, and so on), in order to speed up James, lots of parallelisms have been introduced. All went fine until have discovered that the parallelism was killing our performances.
At this point, we have decided to go reactive with Reactor, here is what we have learned.

Tags

Reactive systems

About the speaker

Gautier Di Folco

Gautier Di Folco

Tech Lead at Linagora
After working 3 years in the embedded and security software development, Gautier now works for Linagora, on Apache James, an Open Source mail server. His…
Read more

Other videos that you might like

fallback image
Reactive systems
Alpakka – a new world of Connectors for Reactive Enterprise Integration
Jan Pustelnik
fallback image
Reactive systems
Events-first microservices with Lagom
Kenny Baas, Gideon de Kok
fallback image
Reactive systems
Beyond the hype: reactive vs traditional microservices
Marcin Zagórski, Paweł Dolega, Łukasz Biały
fallback image
Reactive systems
Stream Driven Development with Akka Streams
Stefano Bonetti
All videos