Deploying Reactive Microservices

Chapter 1. Introduction

Every business out there now is a software company, is a digital company.

Satya Nadella, Ignite 2015

This report is about deploying Reactive microservices and is the final installment in this Reactive microservices series. Jonas Bonér introduces us to Reactive and why the Reactive principles so inherently apply to microservices in Reactive Microservices Architecture. Markus Eisele’s Developing Reactive Microservices explores the implementation of Reactive microservices using the Lagom Framework. You’re encouraged to review those works prior to reading this publication. I will presume basic familiarity with Reactive and the Reactive Manifesto.

Thus far in the series, you have seen how adherence to the core Reactive traits is critical to building services that are decoupled but integrated, isolated but composable, extensible and maintainable, all while being resilient and scalable in production. Your deployment systems are no different. All applications are now distributed systems, and distributed applications need to be deployed to systems that are equally designed for and capable of distributed operation. At the same time, the deployment pipeline and cluster can inadvertently lock applications into container-specific solutions or services. An application that is tightly coupled with its deployment requires more effort to be migrated to another deployment system and thus is more vulnerable to difficulties with the selected provider.

This report aims to ...