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

Refactoring homework


The refactoring homework for this chapter will involve getting rid of unfiltered and dispatch it in the bookstore-code base and replacing it with Akka HTTP. I have done the work of creating the framework-level code that you will build on top of. I'll break down what needs to be done for both outbound and inbound HTTP changes separately, in the following sections. As always, you will do your work in the -incomplete code base, and you can consult what I did in the -complete code base if you get stuck.

Inbound HTTP changes

Your inbound HTTP homework will involve creating Akka HTTP routes for the sales-order-processing and user-management modules. I have already fully updated the routes handling code in the inventory-services module. You can look at it and let it serve as the guide on how you finish the changes in the other modules. One thing you will notice is that the api root is not contained in the routes definition. As this is a common concern across all routes, it is...

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