This book is a part of Knoldus Reactive Programming Series. A few years ago, applications were much simpler and required all solutions at one place, we call them monolithic applications. Now a days markets are changing rapidly. You either adapt quickly or you go out of business. If your application is successful, you will start enhancing features day by day and as a result, your application becomes complex day by day and that complexity creates challenges in development. It will be difficult to fully understand and made changes fast and correctly. You must redeploy the entire application on each update. These type of application also has a barrier to adopting new technologies because it will affect the entire application. In this book, you will learn how you can manage this problem by dividing project into smaller pieces.
You will learn how quickly you can start transforming your monolithic application into microservices. Microservice can be developed using different programming language (Personally I don’t suggest to do it). I prefer Akka HTTP because it is fully integrated into Typesafe stack. Since there are already a lot of scala frameworks to build REST APIs then the obvious question is Why Akka HTTP? There are many reasons to use Akka HTTP, which you will learn in this book.
I have written this book for those who want to start developing REST API right away and have a basic understanding of Scala. I don’t exhaustively list all feature of Akka HTTP. I don’t make you suffer through long and contrived example. I have tried to explain every topic of this book with short and easy to understand examples with test-cases.
Akka HTTP is available for both Java and Scala but in this book, we will go with Scala. I choose Scala because it cuts down on boilerplate and we can concentrate on the logic of our problems. In Scala, you are not limited to just object-oriented patterns to implement your code, you can bring in functional paradigms as well.