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

Design


One of the best ways to design a software system is to capture the business domain, its users, and their interaction with the system as a user story (https://en.wikipedia.org/wiki/User_story). User stories are an informal way of capturing the requirements of a software system. In user stories, the focus is on the end users and the interactions that are possible between the users and the system.

Users and entities

The first step in writing user stories for the Helping Hands application is to understand the users and entities of the system. Primarily, there are two users of the system—Service Consumers and Service Providers, as shown in the following diagram. Service Consumers subscribe to one or more services provided by the Service Providers. The core entity of the application is the service. A service is an intangible, temporal, and limited asset that providers own and provide to the consumers on-demand at a price.

 

Service Providers register one or more services with the system that...