[erlang-questions] New Feature added to Erlang

[Fred Hebert]

I would recommend making a better use of the network in such cases.

There are various options available: use the socket buffers as a storage
mechanism. Each port can be mapped to specific memory addresses and
pushing data on there (and subsequently reading and pushing back data on
there) can be used to offload some state.

Moreover, I would recommend each Erlang node has a 'ping' interface, or
a delayed ping interface. Overloading memory can be sent over the
network that way, and the delayed ping will make use of other nodes'
buffers and also the actual cables and connections between computers as
an 'in-flight' memory storage.

This is similar to old lamps from back in the day where you had a given
time interval worth of data to store in the electrical loop going
through the lamp. In this day and age with the cloud and
multi-datacenter connections, it becomes excessively cheap to achieve
high latencies between data centers.

Using this, and computers purposedly placed far away as to create
latency, it is possible to store data in flight over the network. I
would recommend writing a new RFC that has ISPs and other providers
placing Internet nodes at various strategic points whose sole purpose
will be to mirror back data so that various services can overflow their
memory to the network.

Regards,
Fred.

On 04/01, Joe Armstrong wrote:
> http://joearms.github.com/2013/04/01/too-big-to-fail.html
> 
> /Joe

> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions