深入探索Reactive编程：RxJava实战

需积分: 10 162 浏览量更新于2024-07-15 收藏 7.74MB PDF 举报

"Reactive Programming with RxJava.pdf" RxJava是一种针对Java和Android的响应式编程实现，它受到函数式编程的影响。响应式编程的核心思想是通过数据流和变换来处理异步和事件驱动的程序。它从观察者模式出发，即生产者/消费者回调，并扩展了数十个操作符，用于组合、转换、调度、限制速率、错误处理以及生命周期管理。本书"Reactive Programming with RxJava"由Tomasz Nurkiewicz和Ben Christensen撰写，Erik Meijer作序。书中的内容深入探讨了RxJava的概念和用法，作者们基于他们在实际项目中大量使用RxJava的经验，提供了宝贵的见解。Erik Meijer高度评价此书，认为它是进入响应式编程领域的最佳途径。在现代Android应用开发中，RxJava是管理高度状态化、并发和异步实现的宝贵工具。Jake Wharton，Square公司的软件工程师，指出这本书不仅是逐步学习RxJava的好教材，也是理解这个库的一个重要参考，因为RxJava本身可能对初学者来说相当复杂。 Tomasz和Ben擅长用简单明了的方式解释复杂的概念，使得本书阅读起来轻松愉快，对于任何想要掌握JVM平台响应式编程的开发者来说，都是必备读物。书中涵盖了如何创建异步、事件驱动的应用，帮助读者理解如何利用RxJava处理复杂的并发问题，优化应用程序性能，同时提供了关于Android平台的具体应用。通过学习这本书，开发者可以学习到如何使用RxJava来： 1. 实现观察者模式，构建松耦合的组件。 2. 使用操作符进行数据流的组合和转换，如map、filter、concatMap等。 3. 调度任务执行，比如在特定线程上运行操作。 4. 错误处理，通过onErrorResumeNext和onErrorReturn等方法优雅地处理异常。 5. 控制数据流的速率，避免过快的数据导致的问题，如debounce和throttleFirst等操作符。 6. 管理组件的生命周期，确保资源的正确释放。 7. 在Android环境中集成RxJava，优化UI更新和网络请求。 "Reactive Programming with RxJava"不仅提供了一个深入了解RxJava的平台，还为Java和Android开发者提供了实践响应式编程的强大指南，帮助他们构建高效、可维护的异步应用程序。

soft.Phone.Reactive for Windows Phone 7 and started to implement Rx in various

other languages such as JavaScript, and C++, and dabbled with experimental versions

in Ruby and Objective-C.

The first Rx user inside Microsoft was Jafar Husain, and he brought the technology

with him when he joined Netflix in 2011. Jafar evangelized Rx within the company,

and eventually re-architected the Netflix UI’s client-side stack to fully embrace asyn‐

chronous stream processing. Also, most fortunately for all of us, he managed to pass

on his enthusiasm to Ben Christensen who was working on Netflix’s middle tier API

and since Netflix uses Java on the middle tier, Ben started to work on RxJava in 2012

and moved the codebase to Github in early 2013 for continued open source develop‐

ment. Another early adopter of Rx at Microsoft was Paul Betts and when he moved to

Github, he managed to convince his colleagues at Github such as Justin Spahr-

Summers to implement and release ReactiveCocoa for Objective-C in the spring of

2012.

As Rx became more popular in the industry, we convinced Microsoft Open Tech to

open-source Rx .NET in the fall of 2012. Soon thereafter, I left Microsoft to start

Applied Duality and focus 100% of my time on making Rx the standard cross-

language and cross-platform API for asynchronous real-time data stream processing.

Fast forward to 2016 and the popularity and use of Rx has skyrocketed. All traffic

through the Netflix API relies upon RxJava, as does the Hystrix fault-tolerance library

that bulkheads all internal service traffic, and via related reactive libraries RxNetty

and Mantis, Netflix is now creating a completely reactive network stack for connect‐

ing all internal services across machine and process boundaries. RxJava is also

extremely successful in the Android space with companies like SoundCloud, Square,

NYT, Seatgeek all using RxJava for their Android apps and contributing to the RxAn‐

droid extension library. noSQL vendors such as Couchbase and Splunk also offer Rx-

based bindings to their data access layer. Other Java libraries that have adopted

RxJava amongst others include Camel Rx, Square Retrofit, and Vert.x. In the Java‐

Script community, RxJS is widely used and powers popular frameworks such as

Angular 2. The community maintains a website where you can find information

about Rx implementations in many languages, as well as fantastic Marble Diagram

artwork and explanations by David Gross (@CallHimMoorlock).

Since its inception, Rx has evolved with the needs and the input from the developer

community. The original implementation of Rx in .NET focussed squarely on trans‐

forming asynchronous event streams, and used asynchronous enumerable for scenar‐

ios that needed back pressure. Since Java does not have language support for async

await, the community extended the Observer and Observable types with the concept

of reactive pull and introduced the Producer interface. Thanks to many open source

contributors, the implementation of RxJava is also extremely sophisticated and highly

optimized.

xiv | Foreword

“Rx.” At that time, I was pretty comfortable with concurrency but still thought about

it imperatively, and very much in a Java-centric manner, as Java has been my predom‐

inant breadwinner, and thus where I have spent the most time.

So, as Jafar tried selling me on the approach, it was difficult to grasp the concepts due

to their functional programming style, and I pushed back on it. Months of arguments

and discussions followed as the overall system architecture continued maturing, dur‐

ing which Jafar and I continued our many whiteboard sessions until I grasped the

theoretical principles and subsequently the elegance and power of what Reactive

Extensions could offer.

We decided to embrace the Rx programming model in the Netflix API and ultimately

created the Java implementation of Reactive Extensions called RxJava, following the

naming convention started by Microsoft with Rx.Net and RxJS.

In the roughly three years that I worked on RxJava, most of it done in the open on

GitHub, I had the privilege to work with a growing community and 120-plus contrib‐

utors to turn RxJava into a mature product used in many production systems both

server and client side. It has succeeded enough to get more than 15,000 stars on Git‐

Hub, making it one of the top 200 projects, and third highest of projects using Java.

George Campbell, Aaron Tull, and Matt Jacobs at Netflix were essential in maturing

RxJava from early builds to what it became, including the addition of lift, Sub

scriber, backpressure, and JVM-polyglot support. Dávid Karnok became involved in

the project and has now surpassed me in commits and lines of code. He has been a

significant factor in the project’s success and has now taken over as the project lead.

I have to thank Erik Meijer who created Rx while he was at Microsoft. Since he left

that company, I had the opportunity to collaborate with him at Netflix on RxJava, and

now I’m lucky enough to be working directly with him at Facebook. I consider it a

real honor to be able to spend so many hours at a whiteboard with him discussing

and learning. It makes a real difference having a mentor like Erik to level-up one’s

thinking.

Along the way I also got to speak at many conferences about RxJava and reactive pro‐

gramming, and through that process met many people who have helped me learn far

more about code and architecture than I would have ever done on my own.

Netflix was phenomenal in supporting my time and efforts on the project as well as

providing support for technical documentation that I could have never written by

myself. Open source of this maturity and scope does not succeed without being able

to do it during your “day job” and with the involvement of many people with different

skillsets.

xviii | Introduction

剩余371页未读，继续阅读

mikeleishen

粉丝: 4

深入探索Reactive编程：RxJava实战

深入探索Reactive Programming with RxJava：异步事件驱动开发

深入探索Reactive Programming：RxJava实战

Node.js响应式编程实战

Reactive Programming with RxJava pdf 0分

Reactive Programming with RxJava mobi

Reactive Programming on Android with RxJava (2017).pdf

LEARNING_REACTIVE_PROGRAMMING_WITH_JAVA_8.pdf

Reactive+Programming+With+Java+9-Packt+Publishing(2017).pdf

Reactive Android Programming PDF

Getting started with Spring Framework: covers Spring 5（epub）

最新资源