All videos
All videos
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
Other videos that you might like
Beyond the hype: reactive vs traditional microservices
Marcin Zagórski, Paweł Dolega, Łukasz Biały
Monitoring Akka with Kamon 1.0
Steffen Gebert
Panel discussion on Reactive Systems
Samuel Weiss, Trevor Burton-McCreadie, Łukasz Biały, Alan Klikić, Paweł Dolega
The right way to test your application
Paweł Kamiński