Download as PDF, PPTX
![REACTIVE NETTY
RX NETTY
https://github.com/Netflix-Skunkworks/WSPerfLab/blob/master/test-results/RxNetty_vs_Tomcat_April2015.pdf
CPU saturated
clients
req/s avg lat [ms]](https://image.slidesharecdn.com/901311ad-7417-4894-b673-ba1b77f5af80-151212100455/75/rx-java-presentation-40-2048.jpg)
Uploaded byMateusz Bukowicz
rx-java-presentation
RxJava is a library for composing asynchronous and event-based programs using observable sequences for the Java VM. It provides APIs for asynchronous programming with observable streams. Reactive Extensions (Rx) is a library that supports reactive programming with observable streams in many languages. Netflix adopted RxJava to address issues with its legacy API and improve performance of its services. RxJava uses Observables to build responsive and resilient applications in a reactive style.
![[OpenStack Days Korea 2016] Track1 - 카카오는 오픈스택 기반으로 어떻게 5000VM을 운영하고 있을까?](https://cdn.slidesharecdn.com/ss_thumbnails/16kakao-160226171853-thumbnail.jpg?width=640&height=640&fit=bounds)
rx-java-presentation
- 1.
- 2.
- 3. REACTIVE SUPPORT INDIFFERENT LANGUAGES REACTIVE EXTENSIONS ▸ Rx.Net ▸ RxJava ▸ RxJS ▸ RxScala ▸ RxClojure ▸ RxCpp ▸ Rx.rb ▸ RxPY ▸ RxGroovy ▸ RxJRuby ▸ RxKotlin ▸ RxSwift
- 4. HOW IT BEGAN RX.NET ▸Rx.NET released in 2009 ▸ Shipped with .NET 4.0 (2010)
- 5. AN API FORASYNCHRONOUS PROGRAMMING WITH OBSERVABLE STREAMS. reactivex.io DEFINITION
- 6.
- 7. WHAT IS REACTIVE? REACTIVEMANIFESTO ▸ responsive ▸ resilient ▸ elastic ▸ message-driven
- 8. REACTIVE CAN BEREPULSIVE REACTIVE MANIFESTO CONTROVERSY
- 9. REACTIVE AS ALIFESTYLE REACTIVE PROGRAMMING
- 10. OLD WAY OFDOING THINGS PROCEDURAL WAY
- 11. FROM PROCEDURAL TOFUNCTIONAL FUNCTIONAL WAY
- 12. FROM FUNCTIONAL TOREACTIVE REACTIVE WAY
- 13. HOW TO OBSERVE? ITERABLEVS OBSERVABLE http://reactivex.io/intro.html
- 14.
- 15.
- 16.
- 17.
- 18. WHICH OPERATORS SHOULDI USE? OPERATORS DECISION TREE http://reactivex.io/documentation/operators.html#tree
- 19. NETFLIX OLD WAY- PROBLEM http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
- 20. NETFLIX OLD WAY- PROBLEM http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
- 21. NETFLIX OLD WAY- PROBLEM http://techblog.netflix.com/2013/01/optimizing-netflix-api.html
- 22. NETFLIX NEW WAY- SOLUTION http://techblog.netflix.com/2013/01/optimizing-netflix-api.html
- 23. THINK ABOUT THEFUTURE single item multiple items sync T getData() Iterable<T> getData() async Future<T> getData() ? List<Future<T>> getData()
- 24. A NEW GUYCOMES IN RX.NET IS SO COOL
- 25. OBSERVABLE TO THERESCUE single item multiple items sync T getData() Iterable<T> getData() async Future<T> getData() Observable<T> getData()
- 26. NETFLIX NEW WAY- SOLUTION http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
- 27. NETFLIX NEW WAY- SOLUTION http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
- 28.
- 29. PARALLEL WORK CONCURRENCY ▸ mostoperators - synchronous by default ▸ some operators - implicit concurrency ▸ programmatic concurrency: observeOn/subscribeOn
- 30.
- 31.
- 32.
- 33.
- 34. ERROR HANDLING ON ERRORRESUME NEXT http://reactivex.io/documentation/operators/catch.html
- 35. OH, MY BACK! BACKPRESSURE
- 36.
- 37. BACK PRESSURE ON BACKPRESSUREBUFFER https://github.com/ReactiveX/RxJava/wiki/Backpressure
- 38. MORE RESILIENT RX.JAVA HYSTRIX+ RX.JAVA https://github.com/Netflix/Hystrix/wiki/How-To-Use#Reactive-Execution
- 39. CIRCUIT BREAKER CLOSED OPENHALF-OPEN failure threshold reached timeouttimer expired operation failed success count threshold reached always return failure increment failure counter on failure increment success counter on success start
- 40. REACTIVE NETTY RX NETTY https://github.com/Netflix-Skunkworks/WSPerfLab/blob/master/test-results/RxNetty_vs_Tomcat_April2015.pdf CPUsaturated clients req/s avg lat [ms]
- 41. RX NETTY VSTOMCAT WHY RX NETTY IS BETTER? ▸ lower CPU consumption ▸ lower object allocation rate/less GC ▸ event loop architecture vs thread pool architecture ▸ no thread pool locks ▸ less thread migrations ▸ more CPU Instructions Per Cycle (IPC) https://github.com/Netflix-Skunkworks/WSPerfLab/blob/master/test-results/RxNetty_vs_Tomcat_April2015.pdf
- 42. REACTIVE STREAMS -INITIATIVE http://www.reactive-streams.org
- 43. REACTIVE STREAMS -SCOPE http://www.reactive-streams.org
- 44. FUTURE IS REACTIVE JAVA9 FLOW API ▸ JDK 9.0 ▸ RxJava 2.x -> Reactive Streams implementation ▸ JPA -> Hibernate ▸ Reactive Streams -> RxJava 2.x
- 45.