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

需积分: 5 160 浏览量更新于2024-06-15 收藏 10.85MB PDF 举报

"Reactive Programming with RxJava是关于如何使用RxJava创建异步、基于事件的应用程序的专业书籍，适合想要同时提升英语和编程技能的读者。本书由Tomasz Nurkiewicz和Ben Christensen撰写，并得到了Erik Meijer的序言推荐。书中涵盖了Android方面的内容，适合Java开发者，尤其是对RxJava和反应式编程感兴趣的读者。" RxJava是一种在Java虚拟机（JVM）上运行的库，它允许开发人员通过使用可观察序列来处理异步数据流。反应式编程是一种编程范式，它以声明性方式处理事件和数据流，强调数据流和变换，而不是控制流。这种编程风格特别适合于处理复杂的并发和事件驱动的系统，如现代的Android应用程序。本书深入探讨了RxJava的核心概念和用法，包括但不限于以下几个方面： 1. 可观察序列：RxJava的基础是可观察序列，这是一个可以发送数据或完成/错误信号的对象。开发者可以通过订阅这些序列来响应数据变化。 2. 操作符：RxJava提供了一系列操作符，用于转换、过滤、合并、延迟等数据处理任务。例如，map操作符用于应用函数到每个元素，filter用于筛选元素，concat和merge用于组合多个可观察序列。 3. 调度器：调度器在反应式编程中用于控制操作的执行位置和时间，比如在主线程还是后台线程。这有助于确保UI更新和IO操作的正确同步。 4. 错误处理：RxJava通过异常传播和错误处理机制，使得错误可以在数据流中被优雅地处理和传递。 5. 状态管理和生命周期：在Android环境中，应用的组件（如Activity和Fragment）有特定的生命周期。RxJava提供了与这些生命周期结合的方法，以防止内存泄漏和未处理的订阅。 6. 分布式和微服务：反应式编程模式也适用于构建分布式系统和微服务，因为它天生支持解耦和响应式扩展。 7. 实践案例：书中包含了大量的实际示例和最佳实践，帮助读者将理论知识应用于实际项目。通过阅读这本书，读者将能够掌握如何利用RxJava构建高效、健壮且易于维护的异步应用程序，无论是针对Android平台还是其他JVM环境。同时，书中的实例和作者的经验分享将有助于简化理解这个强大的工具，使开发者能够更好地应对并发挑战和复杂的数据处理场景。

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页未读，继续阅读

我有个朋友是大曹村的

粉丝: 99
资源: 26

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

Reactive Programming with RxJava epub

Reactive Programming with RxJava mobi

Reactive Programming with RxJava

module "rxjava_reactive-streams-1.0.4" variant "android_common": module source path "vendor/qcom/proprietary/ais/test/Carlog/libs/rxjava/reactive-streams-1.0.4.jar" does not exist 11:37:22 soong bootstrap failed with: exit status 1 报错含义

springboot外文文献

推荐几篇 webflux的培训教程

java Flowable 学习教程

推荐学习 project-reactor的博客

请在配置文件中设置 spring.main.web-application-type=reactive 或者移除 spring-boot-starter-web 依赖。

hibernate reactive panache

最新资源