-
Notifications
You must be signed in to change notification settings - Fork 1
Play! info mix
- 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
- [How is Akka used in Play!] (http://stackoverflow.com/questions/22718905/how-is-akka-used-in-play)
- What is reactive programming
- Introduction to 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)
-
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.
-
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)
-
Future of Play! is Akka-HTTP with reactive streams.
-
Non blocking in Play! is The Play WS API, Sending/receiving messages to/from Akka actors
-
Play project structure has changed few times with new versions
-
Twirl Play! use for view rendering Twirl templating. Is default but you can use others. Is non component based but you have helpers with dynamic html elements in it. Is compiled == type checking, your IDE can helps you like with java code. (type checking). Your views are just scala functions so you can call it. Type checking on compile time.
-
By default is Play! intended work with short requests. If you have not, long request block the Akka component of Play! app. (Akka thread pool is saturating). It can be solved by execution contexts.