Book Image

Microservices with Clojure

By : Anuj Kumar
Book Image

Microservices with Clojure

By: Anuj Kumar

Overview of this book

The microservice architecture is sweeping the world as the de facto pattern with which to design and build scalable, easy-tomaintain web applications. This book will teach you common patterns and practices, and will show you how to apply these using the Clojure programming language. This book will teach you the fundamental concepts of architectural design and RESTful communication, and show you patterns that provide manageable code that is supportable in development and at scale in production. We will provide you with examples of how to put these concepts and patterns into practice with Clojure. This book will explain and illustrate, with practical examples, how teams of all sizes can start solving problems with microservices. You will learn the importance of writing code that is asynchronous and non-blocking and how Pedestal helps us do this. Later, the book explains how to build Reactive microservices in Clojure that adhere to the principles underlying the Reactive Manifesto. We finish off by showing you various ways to monitor, test, and secure your microservices. By the end, you will be fully capable of setting up, modifying, and deploying a microservice with Clojure and Pedestal.
Table of Contents (18 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Monitoring microservices


A microservices-based application is highly flexible in terms of deployment and scaling. It consists of multiple services that may have one or more instances running on a cluster of machines across the network. In such a highly distributed and flexible environment, it is of utmost importance that each instance of a microservice is monitored in real time to get a clear view of the deployed services, their performance, and to capture issues of interest that must be reported as soon as they occur. Since each request to a microservice-based application may span out to one or more requests among microservices, there should be a mechanism to track the flow of requests and also locate the areas of bottleneck that can be addressed by performing a root cause analysis and often scaling the services further to meet the demand.

One of the ways to set up an effective monitoring system is to collect all the metrics across the services and machines and store them in a centralized...