We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Democratizing event processing at all scales and platforms with Reactive Extensions

Formal Metadata

Title
Democratizing event processing at all scales and platforms with Reactive Extensions
Alternative Title
Scaling Event Processing at all scales and all languages with the Reactive Extensions
Title of Series
Number of Parts
170
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Modern applications are highly connected applications, often consuming several asynchronous or stream-based services. This makes users happy, but can easily lead to code that is a nightmare to develop and maintain. Enter Reactive Extensions, also known as Rx. Rx can help tame callback hell and can abstract away the notion of time, turning asynchronous requests into observable sequences. Just as we can query normal sequences such as collections, these observable sequences can be composed through either standard query operators (e.g., filter, project, aggregate) or even temporal ones (e.g., “sample a noisy event stream at 100ms intervals”). In this talk, we’ll cover the JavaScript, .NET, C++, Ruby and Python and even RxJava. Use Rx wisely, and may your web service never be crashed by the weight of its own popularity!