mria VS otp

Mria is an open source extension to Mnesia that adds eventual consistency to clusters. Most of the features described earlier still apply to it, the difference is how data is replicated between nodes. Mria switched from a full mesh topology to a mesh+star topology. Each node assumes one of two roles: core node or replicant node.

In EMQX 5.0, we attempted to mitigate this issue in a new DB backend type called RLOG (as in replication log), which is implemented in Mria. Mria is an extension to the Mnesia database that helps it scale horizontally by defining two types of nodes: i) core nodes, which behave as usual Mnesia nodes and participate in write transactions; ii) replicant nodes, which do not take part in transactions and delegate those to core nodes, while keeping a read-only replica of the data locally. This helps to reduce the risk of split-brain scenarios and lessens the coordination needed for transactions, since fewer nodes participate in it, while keeping read-only data access fast, since data is available locally for reading in all nodes.

Mria is an open-source extension to Mnesia that adds eventual consistency to the cluster.

> write-up soon as a guide for Python developers moving to Elixir

Awesome initiative!

> ETS as a KV/document store to hold user and application state and then reacting to changes in to that the way you are here

This is actually pretty interesting. I can't speak to ETS but Mnesia has replication and you can expose the replication log using something like https://github.com/emqx/mria. I've only had a cursory look at this so I could be wrong about its capabilities but it would be an awesome extension to the new Realtime if possible.

Theoretically, you could install any version that appears in https://github.com/erlang/otp/releases. Since it is compiled and installed from source, the installation process will take some time. When you see the following message, the installation is complete.

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

You can read my original report and subsequent PRs in Erlang/OTP here: https://github.com/erlang/otp/issues/5811

- a massive speedup of a common static analyzer for Erlang (https://github.com/erlang/otp/pull/5997)

Funny that you should mention Erlang. Looking at the Github for Erlang, it appears that the source for Erlang is 16.8% written in C. I would bet these are not the least important bits of the whole thing. So, Erlang depends on C.

It looks more like some of the JIT improvements made it profitable to manually unroll some loops in the base64 module: https://github.com/erlang/otp/commit/a03cf1601605dee767cd9d5...

https://github.com/erlang/otp as far as I know. It's somewhat confusing and I honestly couldn't say exactly where the BEAM VM or OTP or ERTS (Erlang Runtime System) start and end. I've never dug into it. I just install Elixir and sometimes Erlang through the ASDF tool, which does all the compiling for me.