[erlang-questions] design pattern question for messaging
Thu Jul 24 00:35:39 CEST 2014
Mark Allen wrote:
> On 7/23/14 3:31 PM, "Miles Fidelman" <mfidelman@REDACTED> wrote:
>> I keep coming back to wishing for an environment where the basic "unit
>> of computation" has both actor-like properties and object-like
>> properties. Long term persistence, data encapsulation, plus
>> message-passing concurrency. Erlang seems to be the best starting point
>> that I've found.
> Have you considered Microsoft's Orleans run-time environment?
> It sounds like it might fit into the concepts you're thinking about. I
> think it's pretty cool. I'd love to see some of these concepts in the
> Erlang run-time, especially as a update/alternative for the current
> distributed Erlang model.
This is the first I've heard of it. Thanks for the pointers!
Some interesting concepts - particularly the notion of persistent actors
that never go away.
As soon as I see .net, though, I start cringing. And Microsoft is known
for developing interesting stuff in the lab, that then goes away (at
least they publish it though, Apple tends to deep six things.)
As you say - some of those concepts might fit, and might be nice to pull
into the Erlang environment.
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
More information about the erlang-questions