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)

Pitfalls

We now have a working application that seems to work reasonably well. Each microservice is an independent autonomous unit that does one thing and does it well. Nothing is shared across microservices, and they seem to remain independent.

Our microservices are all non-blocking and asynchronous in their internal implementation and communication with external services. We have adequately handled implicitly-blocking database calls by letting Slick take care of all the pain, and in turn, providing us with an asynchronous API.

So, we have fundamentally executed everything we learned up until now in this book, in this chapter. However, are we still good enough?

Service locator: If the rank-app microservice needs to make an HTTP call to so-app, it needs to have the URL of the so-app microservice. Currently, this URL is provided by the config file to rank-app. This is a fragile...