distributed Actors for Java 8 http://ruedigermoeller.github.io/kontraktor/
Java JavaScript Shell
Latest commit f0052a8 Aug 22, 2016 @RuedigerMoeller Merge remote-tracking branch 'origin/trunk' into trunk
Conflicts:
	modules/kontraktor-reallive/pom.xml
Permalink
Failed to load latest commit information.
attic bump version, fix errorneous actor blocked ex Oct 30, 2015
examples . Aug 22, 2016
modules Merge remote-tracking branch 'origin/trunk' into trunk Aug 22, 2016
src . Jun 11, 2016
.gitignore . Apr 23, 2016
LICENSE added license Jun 22, 2015
README.md Update README.md Sep 28, 2015
pom.xml . Aug 22, 2016
release.sh . Feb 14, 2016

README.md

kontraktor 3

high performance, lightweight and boilerplate free distributed eventloop'ish Actor implementation designed for Java 8.

Kontraktor enables you to abstract away the network layer used. So any server/service built with kontraktor can be made available via TCP (blocking or NIO), WebSockets, Http Long Poll out of the box. Either with binary serialization or JSon encoding.

JavaScript interop + webserver specialized on SPA's included.

Kontraktor is high performance, you can do up to 2 million point2point async remote calls per second over tcp.

WebSite: http://ruedigermoeller.github.io/kontraktor/

Kontraktor remoted Reactive Streams

3.0 documentation.

Examples: https://github.com/RuedigerMoeller/kontraktor/tree/trunk/examples

Blogposts:

http://java-is-the-new-c.blogspot.de/2015/07/polymer-webcomponents-served-with-java.html

Maven

see http://ruedigermoeller.github.io/kontraktor/#maven

what changed compared to 2.0 ?

  • simplified thread scheduling model. An Actor has a fixed assigned thread. Many actors can be scheduled on the same thread explicitely, no "magic" auto-scaling + pool execution. In the end its important to know what's going on, especially when mixing actors and idiomatic java style block-all-the-threads concurrency.
  • rewrote and redesigned remoting layer such that a minimum of transport specific code is required. Reduces errors as most part of remoting logic is shared accross all transport options (tcp, tcp nio, websocket, http long poll, fst-serialization, json-serialization).
  • changed naming of concurrency primitives EcmaScript 6/7 style. In 2.0 Future clashed with JDK, so now Future became IPromise. Also concurrency tooling has been renamed ES6/7 alike: race, all, yield, await. As the concurrency model is similar to Node.js (difference: we can run N instances, we have threads :) ), this seemed the best option to avoid alienation, at the same time prevent name clashes with java.util.concurrent.
  • JavaScript + SPA interop

Old Blogposts (samples are of OLD 2.0 version, would need minor rewrite (mostly Future => IPromise):