Packt+ | Advance your knowledge in tech

You're reading from Scala Reactive Programming Build scalable, functional reactive microservices with Akka, Play, and Lagom

Product type Paperback

Published in Feb 2018

Publisher Packt

ISBN-13 9781787288645

Length 552 pages

Edition 1st Edition

Languages

Scala

Tools

Akka

Concepts

Microservices

Author (1):

Rambabu Posa

View More author details

Table of Contents (22) Chapters

Title Page

Dedication

Packt Upsell

Contributors

Preface

1. Getting Started with Reactive and Functional Programming FREE CHAPTER

2. Functional Scala

3. Asynchronous Programming with Scala

4. Building Reactive Applications with Akka

5. Adding Reactiveness with RxScala

6. Extending Applications with Play

7. Working with Reactive Streams

8. Integrating Akka Streams to Play Application

9. Reactive Microservices with Lagom

10. Testing Reactive Microservices

11. Managing Microservices in ConductR

12. Reactive Design Patterns and Best Practices

13. Scala Plugin for IntelliJ IDEA

14. Installing Robomongo

1. Other Books You May Enjoy

Leave a review - let other readers know what you think

Index

The Circuit Breaker pattern

In this section, we will discuss another popular and frequently used Reactive Design Pattern: the Circuit Breaker Design Pattern.

Understanding the Circuit Breaker pattern

A Circuit Breaker is one of the most popular and frequently used Reactive Design Patterns. It deals with our Reactive System Stability-related issues. It helps our Reactive System to deal with our System's dependency issues, such as down, crashed, slow performance, restart, and so on.

This Circuit Breaker component finds those dependency issues and stops the sending of further requests so that our system does not waste allocating resources, and also our end users immediately see some error message such as System is unavailable, please try again later.

The Circuit Breaker waits for a predefined amount of time and again tries to send one request to those dependencies (external system or components) and sees the results. If it receives a failure error again, then it waits for some time. If it receives...