sorted by: recent | see : popular

Content Tagged with erlang + scalability

In an earlier post, I had talked about scaling out the service layer of your application using actors and asynchronous processing. This can buy you some more donuts over and above your current throughput. With extra processing in the form of n actors pounding the cores of your CPU, the database will still be the bottleneck and SPOF. As long as you have a single database, there will be latency and you will have to accept it.

Scalaris is a distributed key-value store.

notes on using XMPP as pubsub middleware.

Scala/Lift with RabbitMQ - "the implementation, on its face, looks wicked cool. Erlang at the backend, for high performance reliable messaging being throttled out by Scala actors in the application layer"

Scaling out messaging applications with Scala Actors and AMQP

actor model in Java