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)

AWS resources dashboard

My team and I were tasked with building a web-based dashboard for AWS. This dashboard would allow developers to log in using their BubbleCorp credentials, and, once authenticated, create new CloudFormation environments, as well as visualize the status of each individual resource within a CloudFormation stack.

The application itself is fairly involved, so we will focus on a subset of it: interfacing with the necessary AWS services, in order to gather information about the status of each individual resource in a given CloudFormation stack.

Once it has been finished, this is what our simplified dashboard will look like:

It will display the ID, the type, and the current status of each resource. This might not seem like much right now, but given that all of this information is coming from different, independent web services, it would be far too easy to end...