sorted by: recent | see :
popular
Content Tagged with erlang + scala
Event-Based Programming without Inversion of Control | Lambda the Ultimate
Link to the paper with the same name by Martin Odersky
Ruminations of a Programmer: Erlang as middleware
Using erlang middleware with scala actors
Actor Exceptions
Note the handy comment from Julian Morrison.
Ruminations of a Programmer: Lean Data Models and Asynchronous Repositories
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.
Ruminations of a Programmer: Actors in the Service Layer - Asynchronous and Concurrent
Exploit the virtues of immutability. Design your application around stateless abstractions interacting with each other through asynchronous message passing. These are some of the mantras that I have been trying to grok recently. In a typical Java EE application, we design the service layer to be maximally stateless. What this means is that each individual service has localized mutability interacting with other services on a shared-nothing basis. Asynchronous message passing offers some interesting avenues towards scaling up the throughput of such service layers in an application.
InfoQ: The multicore crises: Scala vs. Erlang
oh, this is an article
Ruminations of a Programmer: Infinite Possibilities : Classes and Objects on top of Erlang Processes
Infinite Possibilities : Classes and Objects on top of Erlang Processes
Ruminations of a Programmer: Lean Data Models and Asynchronous Repositories
Lean Data Models and Asynchronous Repositories
InfoQ: Presentation: Concurrency: Past and Present
In this presentation from QCon London 2008, Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, Software Transactional Memory, the history of concurrency, alternatives to threads, Erlang, Scala, and recommendations for concurrency in Java.
Page 1 | Next >>
