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)

An introduction to microservices

Gone are the times when developers mainly designed simple applications that could be run in a single environment. Nowadays, we have a plethora of environments and hardware configurations. Our applications process lots of data and serve many customers, often with different needs. This has resulted in a need to create big applications. Software architects have explored ways to create such applications. They have used what we call multitier architecture[1], where there's a clear separation between data management, application processing, and presentation.

Applications that are created using one technology stack and are packaged together as one are called monolithic. We can contrast them with microservices architectures[2], where we structure our application as a collection of loosely coupled services. Each service is responsible for one task...