Book Image

Scala Reactive Programming

By : Rambabu Posa
Book Image

Scala Reactive Programming

By: Rambabu Posa

Overview of this book

Reactive programming is a scalable, fast way to build applications, and one that helps us write code that is concise, clear, and readable. It can be used for many purposes such as GUIs, robotics, music, and others, and is central to many concurrent systems. This book will be your guide to getting started with Reactive programming in Scala. You will begin with the fundamental concepts of Reactive programming and gradually move on to working with asynchronous data streams. You will then start building an application using Akka Actors and extend it using the Play framework. You will also learn about reactive stream specifications, event sourcing techniques, and different methods to integrate Akka Streams into the Play Framework. This book will also take you one step forward by showing you the advantages of the Lagom framework while working with reactive microservices. You will also learn to scale applications using multi-node clusters and test, secure, and deploy your microservices to the cloud. By the end of the book, you will have gained the knowledge to build robust and distributed systems with Scala and Akka.
Table of Contents (16 chapters)

Lagom project structure

In this section, we will discuss the high-level structure of a Lagom project or Lagom service or Lagom microservice. Lagom Framework follows a different approach to organize its project structure. As we are new to this framework, I bet we will definitely get confused about the project structure. If newbies look at a Lagom project for the first time, they won't be able to understand it well.

So it is very important to understand this section to develop our Lagom-based projects in the coming sections.

Lagom Framework has organized its project structure into two parts:

  • API Microservice (or project)
  • Implementation Microservice (or project)
  • Frontend Microservice (or project)

We can create all their microservices as separate projects or combine them into one Reactive System.

There is a very strong reason why they have divided a Lagom project into two projects...