Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Clojure Reactive Programming
  • Table Of Contents Toc
Clojure Reactive Programming

Clojure Reactive Programming

By : Leonardo Borges
4.3 (13)
Buy this Book
close
close
Clojure Reactive Programming

Clojure Reactive Programming

4.3 (13)
By: Leonardo Borges
Buy this Book

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.
Table of Contents (13 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. What is Reactive Programming?
Icon
1. What is Reactive Programming?
Icon
A taste of Reactive Programming
Icon
A bit of history
Icon
Signals and events
Icon
Implementation challenges
Icon
Applications of FRP
Icon
Summary
2
2. A Look at Reactive Extensions
Icon
2. A Look at Reactive Extensions
Icon
The Observer pattern revisited
Icon
Creating Observables
Icon
Manipulating Observables
Icon
Flatmap and friends
Icon
Error handling
Icon
Backpressure
Icon
Summary
3
3. Asynchronous Programming and Networking
Icon
3. Asynchronous Programming and Networking
Icon
Building a stock market monitoring application
Icon
Rolling averages
Icon
Identifying problems with our current approach
Icon
Removing incidental complexity with RxClojure
Icon
Summary
4
4. Introduction to core.async
Icon
4. Introduction to core.async
Icon
Asynchronous programming and concurrency
Icon
core.async
Icon
Rewriting the stock market application with core.async
Icon
Error handling
Icon
Backpressure
Icon
Transducers
Icon
Summary
5
5. Creating Your Own CES Framework with core.async
Icon
5. Creating Your Own CES Framework with core.async
Icon
A minimal CES framework
Icon
Exercises
Icon
A respondent application
Icon
CES versus core.async
Icon
Summary
6
6. Building a Simple ClojureScript Game with Reagi
Icon
6. Building a Simple ClojureScript Game with Reagi
Icon
Setting up the project
Icon
Reagi and other CES frameworks
Icon
Summary
7
7. The UI as a Function
Icon
7. The UI as a Function
Icon
The problem with complex web UIs
Icon
Enter React.js
Icon
ClojureScript and Om
Icon
Building a simple Contacts application with Om
Icon
Intercomponent communication
Icon
Exercises
Icon
Summary
8
8. Futures
Icon
8. Futures
Icon
Clojure futures
Icon
Fetching data in parallel
Icon
Imminent – a composable futures library for Clojure
Icon
The movies example revisited
Icon
Futures and blocking IO
Icon
Summary
9
9. A Reactive API to Amazon Web Services
chevron up
Icon
9. A Reactive API to Amazon Web Services
Icon
The problem
Icon
Infrastructure automation
Icon
AWS resources dashboard
Icon
CloudFormation
Icon
EC2
Icon
RDS
Icon
Designing the solution
Icon
Exercises
Icon
Summary
10
A. The Algebra of Library Design
Icon
A. The Algebra of Library Design
Icon
The semantics of map
Icon
Finding the average of ages
Icon
Applicative Functors
Icon
Gathering stats about ages
Icon
Monads
Icon
Summary
11
B. Bibliography
Icon
B. Bibliography
12
Index
Icon
Index

Designing the solution

We now have all the information we need to start designing our application. We need to coordinate four different API calls per CloudFormation stack:

  • describeStacks: To list all available stacks

  • describeStackResources: To retrieve details of all resources contained in a stack

  • describeInstances: To retrieve details of all EC2 instances in a stack

  • describeDBInstances: To retrieve details of all DB2 instances in a stack

Next, I would like you to step back for a moment and think about how you would design code like this. Go ahead, I'll wait.

Now that you're back, let's have a look at one possible approach.

If we recall the screenshot of what the dashboard would look like, we realize that, for the purposes of our application, the difference between EC2 and RDS resources can be completely ignored so long as each one has the attributes ID, type, and status.

This means whatever our solution may be, it has to somehow provide a uniform way of abstracting the different resource types...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Clojure Reactive Programming
End of Section 9
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options
font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon