Play! info mix

Play! info mix

Play! links

• Node.js vs Play
• BigPipe using Play, RxJava, and Hystrix
• Many play usefull activators
• Ybrikmans Blog
• Play under hood
• Gilt and microservices with scala and play
• Play framework and LinkeidIn
• Play with linkedin

Other links

• What is reactive programming
• Quick start with reactive programming
• rxjava-jdbc
• Performance of frameworks
• Concurrent Programming for Scalable Web Architectures
• Threaded vs. Evented
• [Why events are bad idea] (https://www.usenix.org/legacy/events/hotos03/tech/full_papers/vonbehren/vonbehren_html/index.html)

Some notes

• Deadbolt2 problems described with using JPA https://github.com/schaloner/deadbolt-2-java/blob/master/QuickStart.md

• when you see in terminal

Warning: node.js detection failed, sbt will use the Rhino based Trireme JavaScript engine instead to run JavaScript assets compilation, which in some cases may be orders of magnitude slower than using node.js.

... you need to install Nodejs (for example on Debians apt-get install nodejs). Reason is performance when play run javascript it can be much faster with Nodejs.

• ebean deprecated, use JPA instead. reasons : 1 , 2

• we didnt use Akka-HTTP in this project but rather standard Netty because see. Actually Akka-HTTP is written for typesafe by Spray creators. (Spray creators creates Akka-HTTP.

• [Reactive streams] (https://www.playframework.com/documentation/2.4.x/ReactiveStreamsIntegration) in Play! are highly experimental. There is no Java API for now ! (v 2.4)