Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Akka

You're reading from   Mastering Akka A hands-on guide to build application using the Akka framework

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781786465023
Length 436 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Christian Baxter Christian Baxter
Author Profile Icon Christian Baxter
Christian Baxter
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Building a Better Reactive App FREE CHAPTER 2. Simplifying Concurrent Programming with Actors 3. Curing Anemic Models with Domain-Driven Design 4. Making History with Event Sourcing 5. Separating Concerns with CQRS 6. Going with the Flow with Akka Streams 7. REST Easy with Akka HTTP 8. Scaling Out with Akka Remoting/Clustering 9. Managing Deployments with ConductR 10. Troubleshooting and Best Practices

Understanding the refactored bookstore code


So, we have now completed the remodeling effort to get our anemic model into something more rich and more in line with the building blocks of a good DDD. Now, it's time to dive into the code implementation a little, so that you can understand how the code was written to support this model. If you look at the chapter3 code folder from the code distribution, you will notice that at the top level, it's divided into two root folders: bookstore-app-incomplete and bookstore-app-complete. The folder marked as incomplete will be the one that I will be referencing the code from. It will also be the place where you will do some homework to complete the refactor later in the chapter. The folder marked as complete will be used by you to compare your homework results against my fully completed refactor.

The EntityActor abstract class

The EntityActor abstract class defines the behaviors for our DDD entity actor classes. It's modeled as an FSM, where each of the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image