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

Introducing REST


REST stands for representational state transfer, and defines an architectural style for distributed hypermedia systems. It focuses on creating independent component implementations that are stateless and scale well. Applications that support REST do not store any information about the client state on the server side. Such applications require clients to maintain the state themselves and use the REST-style implementations, such as HTTP APIs exposed by the application, to transfer the state between them and the server. Clients who use the REST API may query the server for the latest state and represent the same state at the client side, thus keeping the client and server in sync.

The state of an application is defined by the state of the entities of the system. Entities can be related to the concept of resources in REST architecture. A resource is a key abstraction of information in REST. It is a conceptual mapping to a set of entities that is defined by the resource identifier...