Book Image

Akka Cookbook

By : Vivek Mishra, Héctor Veiga Ortiz
Book Image

Akka Cookbook

By: Vivek Mishra, Héctor Veiga Ortiz

Overview of this book

Akka is an open source toolkit that simplifies the construction of distributed and concurrent applications on the JVM. This book will teach you how to develop reactive applications in Scala using the Akka framework. This book will show you how to build concurrent, scalable, and reactive applications in Akka. You will see how to create high performance applications, extend applications, build microservices with Lagom, and more. We will explore Akka's actor model and show you how to incorporate concurrency into your applications. The book puts a special emphasis on performance improvement and how to make an application available for users. We also make a special mention of message routing and construction. By the end of this book, you will be able to create a high-performing Scala application using the Akka framework.
Table of Contents (18 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Creating a ConsistentHashingPool of actors


In this recipe, you will learn about the ConsistentHashingPool of actors. A ConsistentHashingPool uses consistent hashing to send message to actors.

The idea behind ConsistentHashingPool is that it always forwards a message with the same key to the same actor based on the sent message.

Consistent caching is used for a distributed cache across multiple nodes. It gives us flexibility regarding what is cached and where, for faster results.

Getting ready

To step through this recipe, you need to import a Scala project in our IDE such as IntelliJ Idea. Before we go through the recipe, however, you are required to understand consistent hashing.

For consistent hashing, refer to the following Wikipedia link: https://en.wikipedia.org/wiki/Consistent_hashing.

There are three ways to define the data to use for the consistent hash key:

  • You can define hashMapping of the router to map incoming messages to their consistent hash key. This makes the decision transparent...