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

Creating a microservice for Service Consumer


The Service Consumer microservice exposes APIs for end users to register as a consumer of the Helping Hands application. To look up registered services and place an order, the user of the application must be registered as a Consumer. As per the workflow of Service Consumer defined in Chapter 3, Microservices for Helping Hands Application, it requires the following APIs to create new consumers, get consumer profiles, and update consumer details:

URI

Description

GET /consumers/:id/?flds=name,address

Gets the details of the consumer with the specified :id if the :id is specified, else it gets the details of the authenticated consumer. Optionally, it accepts a CSV of fields to be returned in the response.

PUT /consumers/:id

Creates a new consumer with the specified ID.

POST /consumers

Creates a new consumer and returns the ID.

DELETE /consumers/:id

Deletes the consumer with the specified ID.

Adding routes

Pedestal routes are added for each of the identified APIs...