Deploying Reactive Microservices

Chapter 3. Deploying Reactively

The credit belongs to the man who is actually in the arena.

Theodore Roosevelt, Citizenship in a Republic

Microservices require isolation for elasticity and resilience. Yet by themselves, they are not very useful. Microservices are deployed and managed as systems on clusters. If your deployment system provisions you with well-designed, composable interfaces for handling all the interstitial details, you can deliver your Reactive applications without coding the application to be tightly coupled with its delivery and deployment systems. In this chapter you will deploy a Lagom microservices application using Lightbend Enterprise Suite. You will be using ConductR, which utilizes Akka Actors.

The source code for the example application that you will deploy is available on GitHub. The project’s deploy.md file contains additional information and updates about deploying and testing the sample application project in a wider variety of environments using the latest versions.

The Lagom Chirper application is an example of a service similar to that of Twitter. Instead of tweets, Chirper users post chirps. To be clear, this is only an example and not a complete application. If you are new to developing Reactive microservices, the project can help you better understand how to build a Reactive microservices system using Lagom. You will be using the Chirper application for experimenting with the self-healing properties of Lightbend Enterprise Suite.

The Reactive ...