RxJava反應式編程（影印版 英文版） 下載 mobi epub pdf 電子書 2025

簡體網頁||繁體網頁

☆☆☆☆☆

[美] 托馬什·勒剋威茨本·剋斯藤森 著

齣版社： 東南大學齣版社

ISBN：9787564173708

版次：1

商品編碼：12253966

包裝：平裝

開本：16開

齣版時間：2017-10-01

用紙：膠版紙

頁數：345

正文語種：英文

內容簡介

　　在今天這個手機APP驅動的時代，程序的異步性和響應性至關重要，響應式編程能幫助你編寫更可靠、更易伸縮且性能更好的代碼。在《RxJava反應式編程（影印版 英文版）》這本務實的書中，Java開發者首先會學習到如何用反應式視角看待問題，然後再藉助這一令人興奮的全新編程範式所提供的優秀特性構建應用程序。
　　作者Tomasz Nurkiewicz（托馬什·勒剋威茨）和Ben Christensen（本·剋斯藤森）引入瞭使用RxJava庫的具體例子，解決安卓設備和服務端上的真實性能問題。你會學到RxJava如何利用並行和並發來幫助我們解決今天的問題。
　　《RxJava反應式編程（影印版 英文版）》同時也提供瞭即將發布的2.0版本的預覽。

目錄

Foreword
Introduction
1． Reactive Programming with RxJava
Reactive Programming and RxJava
When You Need Reactive Programming
How RxJava Works
Push versus Pull
Async versus Sync
Concurrency and Parallelism
Lazy versus Eager
Duality
Cardinality
Mechanical Sympathy： Blocking versus Nonblocking I/O
Reactive Abstraction

2． Reactive Extensions
Anatomy of rx．Observable
Subscribing to Notifications from Observable
Capturing All Notifications by Using Observer
Controlling Listeners by Using Subscription and Subscriber
Creating Observables
Mastering Observable．create0
Infinite Streams
Timing： timer（） and interval（）
Hot and Cold Observables
Use Case： From Callback API to Observable Stream
Manually Managing Subscribers
rx．subjects．Subject
ConnectableObservable
Single Subscription with publishO．refCountO
ConnectableObservable Lifecycle
Summary

3． Operators and Transformations
Core Operators： Mapping and Filtering
1-to-1 Transformations Using map（）
Wrapping Up Using flatMap0
Postponing Events Using the delay（） Operator
Order of Events After flatMap0
Preserving Order Using concatMap0
More Than One Observable
Treating Several Observables as One Using merge（）
Pairwise Composing Using zip（） and zipWith（）
When Streams Are Not Synchronized with One Another： combineLatest（），
withLatestFrom（）， and amb（）
Advanced Operators： collect（）， reduce（）， scan（）， distinct（）， and groupBy（）
Scanning Through the Sequence with Scan and Reduce
Reduction with Mutable Accumulator： collect（）
Asserting Observable Has Exactly One Item Using single（）
Dropping Duplicates Using distinct（） and distinctUntilChanged（）
Slicing and Dicing Using skip（）， takeWhile（）， and Others
Ways of Combining Streams： concat（）， merge（）， and switchOnNext（）
Criteria-Based Splitting of Stream Using groupBy0
Where to Go from Here?
Writing Customer Operators
Reusing Operators Using compose（）
Implementing Advanced Operators Using lift（）
Summary

4． Applying Reactive Programming to Existing Applications
From Collections to Observables
BlockingObservable： Exiting the Reactive World
Embracing Laziness
Composing Observables
Lazy paging and concatenation
Imperative Concurrency
flatMap0 as Asynchronous Chaining Operator
Replacing Callbacks with Streams
Polling Periodically for Changes
Multithreading in RxJava
What Is a Scheduler?
Declarative Subscription with subscribeOn（）
subscribeOn0 Concurrency and Behavior
Batching Requests Using groupBy（）
Declarative Concurrency with observeOn（）
Other Uses for Schedulers
Summary

5． Reactive from Top to Bottom
Beating the C1Ok Problem
Traditional Thread-Based HTTP Servers
Nonblocking HTTP Server with Netty and RxNetty
Benchmarking Blocking versus Reactive Server
Reactive HTTP Servers Tour
HTTP Client Code
Nonblocking HTTP Client with RxNetty
Relational Database Access
NOTIFY AND LISTEN on PostgreSQL Case Study
CompletableFuture and Streams
A Short Introduction to CompletableFuture
Interoperability with CompletableFuture
Observable versus Single
Creating and Consuming Single
Combining Responses Using zip， merge， and concat
Interoperability with Observable and CompletableFuture
When to Use Single?
Summary

6． Flow Control and Backpressure
Flow Control
Taking Periodic Samples and Throttling
Buffering Events to a List
Moving window
Skipping Stale Events by Using debounce（）
Backpressure
Backpressure in RxJava
Built-in Backpressure
Producers and Missing Backpressure
Honoring the Requested Amount of Data
Summary

7． Testing and Troubleshooting
Error Handling
Where Are My Exceptions?
Declarative try-catch Replacement
Timing Out When Events Do Not Occur
Retrying After Failures
Testing and Debugging
Virtual Time
Schedulers in Unit Testing
Unit Testing
Monitoring and Debugging
doOn．．．（） Callbacks
Measuring and Monitoring
Summary

8． Case Studies
Android Development with RxJava
Avoiding Memory Leaks in Activities
Retrofit with Native RxJava Support
Schedulers in Android
UI Events as Streams
Managing Failures with Hystrix
The First Steps with Hystrix
Nonblocking Commands with HystrixObservableCommand
Bulkhead Pattern and Fail-Fast
Batching and Collapsing Commands
Monitoring and Dashboards
Querying NoSQL Databases
Couchbase Client API
MongoDB Client API
Camel Integration
Consuming Files with Camel
Receiving Messages from Kafka
Java 8 Streams and CompletableFuture
Usefulness of Parallel Streams
Choosing the Appropriate Concurrency Abstraction
When to Choose Observable?
Memory Consumption and Leaks
Operators Consuming Uncontrolled Amounts of Memory
Summary

9． Future Directions
Reactive Streams
Observable and Flowable
Performance
Migration
A． More HTTP Server Examples
B． A Decision Tree of Observable Operators
Index

精彩書摘

　　《RxJava反應式編程（影印版 英文版）》：
　　You will not see similar low-level implementations outside of the university， but itworks.For each request we ignore whatever was sent to us and return 2000Kresponses.Opening localhost：8080 in the browser succeeds with an OK text reply.The class is named SingleThread for a reason.Serversocket.accept（） blocks untilany client establishes a connection with us.Then， it returns a client Socket.While weinteract with that Socket （read and write to it）， we still listen for incoming connec-tions but no one picks them up because our thread is busy handling first client.It islike at the doctor's office： one patient goes in and everyone else must wait in a queue.Did you notice the extra 100 parameter after 8080 （listening port）？ This value （thedefault is 50） caps the maximum number of pending connections that can wait in aqueue.Above that number， they are rejected.To make matters worse， we pretend toimplement HTTP／1.1 which uses persistent connections by default.Until the clientdisconnects we keep the TCP／IP connection open just in case， blocking new clients.
　　……

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆

評分☆☆☆☆☆