As I understand it the idea is to use an underlying message passing
mechanism which ensures global ordering of asynchronous messages called
"Group Communication". This looks to be easily implementable on top of the
existing Erlang mechanisms.
This is used to propogate committed records to other nodes in one block
rather than write by write while maintaining transaction ordering (and some
other good stuf to do with locking...etc). It claims to remove the problems
of commiting large volumes of complex transactions to many nodes.
Maybe of interest?
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.