Sign In Start Free Trial

Clojure Reactive Programming

By : Leonardo Borges

4.3 (13)

Clojure Reactive Programming

4.3 (13)

By: Leonardo Borges

Overview of this book

If you are a Clojure developer who is interested in using Reactive Programming to build asynchronous and concurrent applications, this book is for you. Knowledge of Clojure and Leiningen is required. Basic understanding of ClojureScript will be helpful for the web chapters, although it is not strictly necessary.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. What is Reactive Programming?

1. What is Reactive Programming?

A taste of Reactive Programming

A bit of history

Signals and events

Implementation challenges

Applications of FRP

Summary

2. A Look at Reactive Extensions

2. A Look at Reactive Extensions

The Observer pattern revisited

Creating Observables

Manipulating Observables

Flatmap and friends

Error handling

Backpressure

Summary

3. Asynchronous Programming and Networking

3. Asynchronous Programming and Networking

Building a stock market monitoring application

Rolling averages

Identifying problems with our current approach

Removing incidental complexity with RxClojure

Summary

4. Introduction to core.async

4. Introduction to core.async

Asynchronous programming and concurrency

core.async

Rewriting the stock market application with core.async

Error handling

Backpressure

Transducers

Summary

5. Creating Your Own CES Framework with core.async

5. Creating Your Own CES Framework with core.async

A minimal CES framework

Exercises

A respondent application

CES versus core.async

Summary

6. Building a Simple ClojureScript Game with Reagi

6. Building a Simple ClojureScript Game with Reagi

Setting up the project

Reagi and other CES frameworks

Summary

7. The UI as a Function

7. The UI as a Function

The problem with complex web UIs

Enter React.js

ClojureScript and Om

Building a simple Contacts application with Om

Intercomponent communication

Exercises

Summary

8. Futures

8. Futures

Clojure futures

Fetching data in parallel

Imminent – a composable futures library for Clojure

The movies example revisited

Futures and blocking IO

Summary

9. A Reactive API to Amazon Web Services

9. A Reactive API to Amazon Web Services

The problem

Infrastructure automation

AWS resources dashboard

CloudFormation

EC2

RDS

Designing the solution

Exercises

Summary

A. The Algebra of Library Design

A. The Algebra of Library Design

The semantics of map

Finding the average of ages

Applicative Functors

Gathering stats about ages

Monads

Summary

B. Bibliography

B. Bibliography

Index

Index

Customer Reviews

4.3 (13)

5 star

76.9%

4 star

0

3 star

7.7%

2 star

7.7%

1 star

7.7%

Futures and blocking IO

The choice of using ForkJoinPool for imminent is deliberate. The ForkJoinPool—added on Java 7—is extremely smart. When created, you give it a desired level of parallelism, which defaults to the number of available processors.

ForkJoinPool then attempts to honor the desired parallelism by dynamically shrinking and expanding the pool as required. When a task is submitted to this pool, it doesn't necessarily create a new thread if it doesn't have to. This allows the pool to serve an extremely large number of tasks with a much smaller number of actual threads.

However, it cannot guarantee such optimizations in the face of blocking IO, as it can't know whether the thread is blocking waiting for an external resource. Nevertheless, ForkJoinPool provides a mechanism by which threads can notify the pool when they might block.

Imminent takes advantage of this mechanism by implementing the ManagedBlocker (see http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ForkJoinPool...

Search

Your notes and bookmarks