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)

Amazon Services use case

The client (which we will call BubbleCorp from now on) had a problem that is all too common and well known in big enterprises: one massive, a monolithic application that had many unrelated business features.

Aside from making the monolithic applications move and evolve slow, as individual components can't evolve independently, such an application makes deployment incredibly difficult, due to its environmental constraints: all of the infrastructure needs to be available in order for the application to work at all.

As a result, developing new features and bug fixes involves having only a handful of development environments, each shared across dozens of developers. This makes for a wasteful amount of coordination between teams just so that they won't step on each other's toes, further slowing down the whole life cycle.

The long-term solution...