Do’s and Don’ts: Avoiding First-Time Reactive Programmer Mines

You want reactive architecture, you know you’re going with WebFlux, you’re fully set up with BlockHound to detect blocking code, and you can tell the difference between Mono and Flux.

What's next? Let’s hit all the possible potholes we can on the road to our first Reactive API. Someone said, "try, fail, and repeat" is the best way to learn. Let's see about that!

Speaker: Sergei Egorov, Staff Software Engineer, Pivotal
Filmed at SpringOne Platform 2019

[ESGreenie]

I really liked this no-hype talk with some clear recommendations and things to avoid. Thank you.

[rafaelbragad]

Awesome presentation! It clarifies a lot how to think about reactive programming!

[agustinernestocardeilhacba]

I am about to drop a tear... Amazing conference !!! :)

[zurumogbonda]

At 16mins in I had to pause and Thank You... Thank You.. valid video

[gunasagar]

Thanks for the great presentation, learned a lot.

[ahmedabdul-aziz]

Great talk I really liked how it's just to the point.

[damienl]

Not sure what happened to the slide share (Uploaded SlideShare Suspended
This SlideShare was suspended because it violated SlideShare Terms of Service and/or Community Guidelines. You can view more SlideShares here.)

[Freeman]

I think there was wrong comparison between Java Streams vs Reactive Streams. Java Streams are actually pull based because we ourselves must call terminal operation like collect() etc. Reactive instead supports push based model when events are coming to us.
Overall useful talk though!

Don't use it for heavy computation?

[iadrianrotaru]

Really nice. But demo is pretty classic. However..how does it work with http interceptors? error handlers? All spring specific aspects to say.

[KalathilAjayMenon]

is having subscribe() really a code smell ?