Book Image

Hands-On Reactive Programming with Clojure - Second Edition

By : Konrad Szydlo, Leonardo Borges
Book Image

Hands-On Reactive Programming with Clojure - Second Edition

By: Konrad Szydlo, Leonardo Borges

Overview of this book

Reactive Programming is central to many concurrent systems, and can help make the process of developing highly concurrent, event-driven, and asynchronous applications simpler and less error-prone. This book will allow you to explore Reactive Programming in Clojure 1.9 and help you get to grips with some of its new features such as transducers, reader conditionals, additional string functions, direct linking, and socket servers. Hands-On Reactive Programming with Clojure starts by introducing you to Functional Reactive Programming (FRP) and its formulations, as well as showing you how it inspired Compositional Event Systems (CES). It then guides you in understanding Reactive Programming as well as learning how to develop your ability to work with time-varying values thanks to examples of reactive applications implemented in different frameworks. You'll also gain insight into some interesting Reactive design patterns such as the simple component, circuit breaker, request-response, and multiple-master replication. Finally, the book introduces microservices-based architecture in Clojure and closes with examples of unit testing frameworks. By the end of the book, you will have gained all the knowledge you need to create applications using different Reactive Programming approaches.
Table of Contents (15 chapters)

Summary

In this chapter, we looked at a different approach on how to handle reactive web interfaces via Om and React. In turn, these frameworks make this possible and painless by applying functional programming principles such as immutability and persistent data structures for efficient rendering.

We also learned to think the Om way by structuring our applications as a series of functions, which receive state and output a DOM representation of state changes.

Additionally, we saw that by structuring application state transitions through core.async channels, we separate the presentation logic from the code, which will actually perform the work, making our components even easier to reason about.

In the next chapter, we will turn to an often overlooked yet useful tool for creating reactive applications—Futures.