[ANN] mnesia_fdb 0.1
Sat Jun 6 18:38:08 CEST 2020
> I’ve heard about foundationDB implemented an actor model in some layer of it’s stack. I’m curious about how it fits into Erlang system, does it act as only a storage backend of Mnesia, or does it also come with its cluster feature like riak does?
They use a library called 'Flow'
(https://apple.github.io/foundationdb/flow.html) to implement
something akin to the actor model.
Since fdb handles the clustering/distribution, transactions etc what
I'm working on is the access layer to the raw key-value store system.
If foundationDB design terms this would be akin to a 'layer'.
Traditionally, mnesia's weak point has been in the distribution layer
(dealing with netsplits etc).
By adding the fdb backend the goal is to offload that responsibility
to fdb, while still enjoying the benefits of the mnesia API.
It's early days and things are not stable, but it is looking promising.
> > On 4/06/2020, at 11:08 PM, Leonard B <leonard.boyce@REDACTED> wrote:
> > Hello,
> > I've been evaluating FoundationDB for a few weeks on another project
> > and it struck me that while it seems promising it was a little odd to
> > work with the NIF driver in erlang.
> > So, in the spirit of community, and building on the great work of the
> > Aeternity (mnesia_rocksdb) and CounchDB (couchdb-erlfdb) tems, I
> > thought having FoundationDB as an alternative mnesia backend may make
> > some sense.
> > This is an early stage announcement as it's just passed the
> > proper-based tests from mnesia_rocksdb.
> > Feedback and issues are welcome as I'm sure things can be improved.
> > Leonard
More information about the erlang-questions