What do you think?
Rate this book
Reactive Web Applications: Covers Play, Akka, and Reactive Streams
Summary
Reactive Web Applications teaches web developers how to benefit from the reactive application architecture and presents hands-on examples using the Play framework.
Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.
About the Technology
Reactive applications build on top of components that communicate asynchronously as they react to user and system events. As a result, they become scalable, responsive, and fault-tolerant. Java and Scala developers can use the Play Framework and the Akka concurrency toolkit to easily implement reactive applications without building everything from scratch.
About the Book
Reactive Web Applications teaches web developers how to benefit from the reactive application architecture and presents hands-on examples using Play, Akka, Scala, and Reactive Streams. This book starts by laying out the fundamentals required for writing functional and asynchronous applications and quickly introduces Play as a framework to handle the plumbing of your application. The book alternates between chapters that introduce reactive ideas (asynchronous programming with futures and actors, managing distributed state with CQRS) and practical examples that show you how to build these ideas into your applications.
What's Inside
About Reader Description
For readers comfortable programming with a higher-level language such as Java or C#, and who can read Scala code. No experience with Play or Akka needed.
About the Author
Manuel Bernhardt is a passionate engineer, author, and speaker. As a consultant, he guides companies through the technological and organizational transformation to distributed computing.
Table of Contents
Reactive Web Applications teaches web developers how to benefit from the reactive application architecture and presents hands-on examples using the Play framework.
Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.
About the Technology
Reactive applications build on top of components that communicate asynchronously as they react to user and system events. As a result, they become scalable, responsive, and fault-tolerant. Java and Scala developers can use the Play Framework and the Akka concurrency toolkit to easily implement reactive applications without building everything from scratch.
About the Book
Reactive Web Applications teaches web developers how to benefit from the reactive application architecture and presents hands-on examples using Play, Akka, Scala, and Reactive Streams. This book starts by laying out the fundamentals required for writing functional and asynchronous applications and quickly introduces Play as a framework to handle the plumbing of your application. The book alternates between chapters that introduce reactive ideas (asynchronous programming with futures and actors, managing distributed state with CQRS) and practical examples that show you how to build these ideas into your applications.
What's Inside
About Reader Description
For readers comfortable programming with a higher-level language such as Java or C#, and who can read Scala code. No experience with Play or Akka needed.
About the Author
Manuel Bernhardt is a passionate engineer, author, and speaker. As a consultant, he guides companies through the technological and organizational transformation to distributed computing.
Table of Contents
328 pages, Paperback
First published March 2, 2016
6 people are currently reading
92 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 3 of 3 reviews
January 20, 2016
(I've reviewed MEAP version with all chapters but before final tuning)
It's better than you may have thought. I've spoken with Manuel earlier this year in Cracow, so I knew it's gonna be good, but it's better than I thought too. What's so good about it?
1. It's an epic "igniter" book & this paradigm works better for paradigms / methods than particular technologies. "Igniter" is a book that gives you the overall concept, foundation & enough of content to push you towards a proper direction. Don't underestimate the last part - many books just give some basic theory & the reader is left with completely no idea how to apply it or where to apply it. RWA does it much better - it helps you to make a first step, but it doesn't either babysit you or pretend that the whole topic has been covered.
2. It's full End-to-End book. It doesn't ignore the front-end specifics of web applications, but gives an idea of approach you could take.
3. It's very practical - it doesn't really follow the bare hype of "everything reactive" - based on what you read, you have a full perspective on what's different in the presented approach.
4. Reactive Streams - 'nuf said.
Cons:
Yes, some.
1. As the book is going through a wide spectrum of technologies, author didn't assume prior knowledge, so there are primers on functional programming, actor model, Play framework, etc. To be honest, it's not a problem & I've read the majority of those even if I didn't need to. Well written.
2. Scala.js? OMG, a step too far ... :)
3. While some chapters are really rich in content (fortunately the most critical ones - like the "Dealing with state" one), some are definitely lacking. I can imagine that author wanted a complete image, but both Deployment & Testing chapters are just too brief (the latter has some interesting ideas though).
Recommended, this is a very good shit.
It's better than you may have thought. I've spoken with Manuel earlier this year in Cracow, so I knew it's gonna be good, but it's better than I thought too. What's so good about it?
1. It's an epic "igniter" book & this paradigm works better for paradigms / methods than particular technologies. "Igniter" is a book that gives you the overall concept, foundation & enough of content to push you towards a proper direction. Don't underestimate the last part - many books just give some basic theory & the reader is left with completely no idea how to apply it or where to apply it. RWA does it much better - it helps you to make a first step, but it doesn't either babysit you or pretend that the whole topic has been covered.
2. It's full End-to-End book. It doesn't ignore the front-end specifics of web applications, but gives an idea of approach you could take.
3. It's very practical - it doesn't really follow the bare hype of "everything reactive" - based on what you read, you have a full perspective on what's different in the presented approach.
4. Reactive Streams - 'nuf said.
Cons:
Yes, some.
1. As the book is going through a wide spectrum of technologies, author didn't assume prior knowledge, so there are primers on functional programming, actor model, Play framework, etc. To be honest, it's not a problem & I've read the majority of those even if I didn't need to. Well written.
2. Scala.js? OMG, a step too far ... :)
3. While some chapters are really rich in content (fortunately the most critical ones - like the "Dealing with state" one), some are definitely lacking. I can imagine that author wanted a complete image, but both Deployment & Testing chapters are just too brief (the latter has some interesting ideas though).
Recommended, this is a very good shit.
October 8, 2019
Useful book to learn about the concepts of the play framework. I'm mostly using it from Java but most of the code examples are easily transferrable. Even as it's an older version of the framework that is discussed many of it will still hold true.
But being interested in the concepts also means instead of learning topics like how to integrate libraries in the exotic scala.js I would have preferred to learn more about higher level concepts, e.g. in this case maybe more on the impact of reactive on frontend development.
But being interested in the concepts also means instead of learning topics like how to integrate libraries in the exotic scala.js I would have preferred to learn more about higher level concepts, e.g. in this case maybe more on the impact of reactive on frontend development.
March 26, 2018
Good, hard to keep up with changes. Chapter on angular is out of date.
Displaying 1 - 3 of 3 reviews