Book Image

Scala Microservices

By : Selvam Palanimalai, Jatin Puri
Book Image

Scala Microservices

By: Selvam Palanimalai, Jatin Puri

Overview of this book

<p>In this book we will learn what it takes to build great applications using Microservices, the pitfalls associated with such a design and the techniques to avoid them. </p><p>We learn to build highly performant applications using Play Framework. You will understand the importance of writing code that is asynchronous and nonblocking and how Play leverages this paradigm for higher throughput. The book introduces Reactive Manifesto and uses Lagom Framework to implement the suggested paradigms. Lagom teaches us to: build applications that are scalable and resilient to failures, and solves problems faced with microservices like service gateway, service discovery, communication and so on. Message Passing is used as a means to achieve resilience and CQRS with Event Sourcing helps us in modelling data for highly interactive applications. </p><p>The book also shares effective development processes for large teams by using good version control workflow, continuous integration and deployment strategies. We introduce Docker containers and Kubernetes orchestrator. Finally, we look at end to end deployment of a set of scala microservices in kubernetes with load balancing, service discovery and rolling deployments. </p><p></p>
Table of Contents (12 chapters)

CQRS

CQRS stands for Command Query Responsibility Segregation. Greg Young has coined this term and most of the literature on the internet regarding CQRS would be associated with him.

In the simplest sense, consider the following scenario:

    UserService.scala
trait UserService{
def createUser(user: User): Unit
def editUser(details: UserDetails): Unit
def deleteUser(user:User): Unit
def getUser(userId: Int): User
def getUserFromName(name: String): User
def getUserPreferences(userId:Int): UserPreference
}

We have a UserService that declares calls to create/get/update users. Applying CQRS would result in splitting UserService into two separate services:

    trait UserReadService {
def getUser(userId: Int): User
def getUserFromName(name: String): User
def getUserPreferences(userId: Int): UserPreference
}

trait UserWriteService...