How we can model the small world phenomenon via the use of actors and events?
Actors vistit certain events and are connected through other actors through the events. In the step/fold process, we develop a network of only actors (where before there was an affiliation network of actors and events) to see whether it is a small world network.
Original ideas from http://nguyentantrieu.info/blog/building-cloud-and-virtual-computing-platform-on-existing-physical-servers/
Philosophy design :
event-driven, scalable, resilient and responsive ( http://www.reactivemanifesto.org )
Open Source Links:
- http://akka.io : a toolkit and runtime for building highly concurrent, distributed, and fault tolerant event-driven applications on the JVM
- https://github.com/peter-lawrey/Java-Chronicle : an ultra low latency, high throughput, persisted, messaging and event driven in memory database
- http://redis.io : advanced key-value store
- http://netty.io : an asynchronous event-driven network application framework
- https://github.com/Netflix/RxJava : a library for composing asynchronous and event-based programs using observable sequences for the Java VM
- http://kafka.apache.org : publish-subscribe messaging rethought as a distributed commit log
- https://github.com/orientechnologies/orientdb/wiki Open Source Graph Database
Reference URLs:
- http://arxiv.org/pdf/1008.1459.pdf : Actor Model of Computation by Carl Hewitt
- http://en.wikipedia.org/wiki/Named_pipe
- http://sonalimendis.blogspot.in/2010/10/named-pipes-for-inter-process.html
- http://www.slideshare.net/drorbr/the-actor-model-towards-better-concurrency
- http://www.aosabook.org/en/nginx.html
- http://www.slideshare.net/joshzhu/nginx-internals
- http://redis.io/topics/pubsub
- http://techblog.netflix.com/2013/01/optimizing-netflix-api.html
