Mnesia distribuida y replicación

Welcome to the final lesson on Mnesia! So far, we've explored Mnesia's fundamentals and how to manage data with transactions. Now, let's unlock its true power: distributed operation.

Distributed Mnesia allows your database to span multiple Erlang nodes, offering incredible benefits for fault tolerance and scalability. Imagine your data staying available even if some servers go down!

For Mnesia to operate across multiple nodes, it needs to know which nodes are part of its cluster. This is managed through an explicit node list.

• Each Mnesia instance on a node is aware of the other nodes.
• It uses Erlang's built-in distribution mechanism to communicate.
• Data can be replicated to or stored on specific nodes in this list.

Without this configuration, Mnesia would only run locally on a single node.

Setting up a distributed Mnesia cluster involves a few key steps:

1. Start Erlang Nodes: Launch each Erlang VM with a unique name (e.g., erl -sname node1@host -setcookie mysecret).
2. Connect Nodes: Ensure all nodes can communicate using net_adm:ping/1.
3. Create Schema: Use mnesia:create_schema/1 on all participating nodes, passing a list of all node names.
4. Start Mnesia: Call mnesia:start/0 on each node.

This establishes the foundation for your distributed database.

This example shows the basic steps to initialize and start Mnesia. In a real distributed setup, you'd run these on each connected node after creating the schema.

Once your Mnesia cluster is set up, you define tables. The key difference for distributed tables is specifying the node_list when creating them.

• The node_list attribute determines which nodes will store copies of the table.
• You can specify different types of copies (disc_copies, ram_copies, disc_only_copies) for each node.
• This allows fine-grained control over data placement and replication.

Mnesia ensures that the table schema is consistent across all nodes in the node_list.

This example shows how to define a table, specifying that it should have disk copies on specific nodes. In a real scenario, 'node1@host' and 'node2@host' would be actual Erlang node names.

Mnesia offers different replication strategies for your table copies:

• disc_copies: Data is stored on disk and loaded into RAM on startup. Provides persistence and fault tolerance.
• ram_copies: Data is only stored in RAM. Fastest access but data is lost if the node crashes (unless replicated elsewhere).
• disc_only_copies: Data is only stored on disk and not loaded into RAM. Slowest access, but uses minimal RAM.

Choosing the right type depends on your persistence, performance, and memory requirements.

When you write data to a distributed Mnesia table, Mnesia ensures atomicity across all nodes involved in the transaction. This means:

• A transaction either commits successfully on all relevant nodes, or it rolls back on all of them.
• Mnesia handles the complexities of two-phase commit protocols behind the scenes.

This guarantees that your data remains consistent, even when spread across a cluster.

Erlang's dynamic nature extends to Mnesia clusters. You can add or remove nodes from a running system without downtime.

• Use mnesia:change_table_copy_type/3 or mnesia:add_table_copy/2 to add new copies of a table to a node.
• Use mnesia:delete_table_copy/2 to remove a copy from a node.

These operations allow you to scale your Mnesia cluster horizontally or perform maintenance.

This is where distributed Mnesia truly shines! By replicating data across multiple nodes, your system becomes highly fault-tolerant.

• If a node with a disc_copies table fails, other nodes with copies can continue serving requests.
• Mnesia automatically synchronizes data when a failed node recovers and rejoins the cluster.
• You can design your system to withstand multiple node failures based on your replication strategy.

This 'always-on' capability is crucial for critical applications.

Which Mnesia table copy type offers the fastest read/write access but loses data if the node crashes and no other copies exist?

Congratulations! You've now learned about configuring and managing distributed Mnesia.

• We covered how to set up Mnesia across multiple Erlang nodes.
• You saw how to define tables with node_list for distribution.
• We explored different replication types: disc_copies, ram_copies, and disc_only_copies.
• Finally, you understand how Mnesia ensures consistency and provides fault tolerance through replication.

Mnesia is a powerful tool for building robust, scalable, and fault-tolerant distributed applications in Erlang.