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)

Why testing is important

At the beginning of this chapter, I pointed out that software testing is important. Why? In order to answer that, you will need to understand what software testing is. It can be defined as a process that ensures that a particular piece of software is bug-free. Testing is a step-by-step process that ensures that the software passes expected standards of performance, set by customers or the industry. These steps can also help to identify errors, gaps, or missing requirements.

The benefits of software testing are as follows:

  • Providing a high-quality product with low maintenance costs
  • Ensuring the accuracy and consistency of the product
  • Discovering defects and errors that are not recognized during the developmental phase
  • Checking whether the application produces the expected output
  • Providing us with knowledge of customers' satisfaction with the product...