Mnesia

Mnesia is a distributed, soft real-time database management system written in the Erlang programming language.[1] It is distributed as part of the Open Telecom Platform.

Mnesia
Original author(s)Joe Armstrong, Robert Virding, Dan Gudmundsson and others
Developer(s)Ericsson
Stable release
4.15.4 / June 19, 2018 (2018-06-19)
Written inErlang
Operating systemCross-platform
PlatformCross-platform
TypeRelational Database Management System
LicenseApache License 2.0 (since OTP 18.0)
Websitewww.erlang.org/doc/man/mnesia.html
LYME (software bundle) is based on Erlang and comprises Mnesia. It is entirely composed of free and open-source software

Description

As with Erlang, Mnesia was developed by Ericsson for soft real-time distributed and high-availability computing work related to telecoms. It was not intended as a general office-based data processing database management system, nor to replace SQL-based systems. Instead Mnesia exists to support Erlang, where DBMS-like persistence is required.[2] It has more in common with embeddable DBMS such as Berkeley DB than with any SQL database server.

Database model

"Rows" in tables are represented as records that contain a key value and a data field. This data field may in turn be a tuple containing an Erlang data structure of any complexity.

Relational features

The database model is relational, but isn't what someone familiar with SQL might expect. A database contains tables. Relationships between them are modelled as other tables.[3]

A key feature of Mnesia's high-availability approach is that tables can be reconfigured within a schema and relocated between nodes, not only while the database is still running, but even while write operations are still going on.

Coding

The query language of Mnesia is Erlang itself, rather than SQL.[4] It permits easy representation of transactions as a natural feature of Erlang by allowing developers to utilize a single language throughout an application.

Transactions

Erlang is a functional language. Mnesia builds on this to obtain ACID transaction support. The functional block which is run as a transaction is a commonplace Erlang construct called a Functional Object (or Fun)[5] and is called by the single Mnesia statement mnesia:transaction(F). This can lead to clearer source code than the paired BEGIN / COMMIT syntax of SQL, and so avoids its problem of unclosed transactions within a procedure.

Again as a result of the functional nature of Erlang, nesting transactions is simple. It's also possible to distribute transactions across multiple nodes (i.e. separate servers). The semantics of using transactions in this way remains consistent, making it easy to write library code that works equally in either context.

General coding style for Mnesia will always use transactions. For performance reasons, it also supports deliberate "dirty operations" which avoid transactions. These compromise the atomicity and the isolation properties of ACID, but offer around 10× more throughput.[6] In addition there are also in-memory alternatives, although these lose the durability property of ACID.

Efficient execution

Mnesia forms part of the LYME web application stack. This is akin to LAMP, but based on Erlang. Implementation in Erlang confers an efficiency benefit because of the use of a single virtual machine throughout an application. LYME makes use of this, since the Yaws web server is also implemented in Erlang.

Address space is shared (although safely so, under Erlang) between code and data, including Mnesia's table data.[1][7]

Origins and licensing

Mnesia and Erlang were developed by the Ericsson Computer Science Laboratory. They have been released as open source software. Mnesia is released under a derivative of the Mozilla Public License.[8] Since OTP 18.0 they are published according to the open source Apache License 2.0. Versions before OTP 18.0 were published under the open source Erlang Public License.[9]

ejabberd

Mnesia is also an option embedded within the Erlang-based Jabber daemon, ejabberd.[10]

gollark: With autoupdate, so if you break one thing you have five minutes or so to fix it before everything updates. It really increases the sense of drama.
gollark: Or you could use the potatOS version control system of having it on pastebin as a gazillion interconnected files.
gollark: There's no way to address individual pixels of the screen or something - you can split characters into sixths, *ish*, using teletext chars, but that's not really the same and you could only make slightly bigger text that way.
gollark: You can't make text smaller than it already is by default.
gollark: You're not helping. Znepb presumably knows what they want.

See also

References
  1. Håkan Mattsson; Hans Nilsson; Claes Wikstrom (1999). "Mnesia - A Distributed Robust DBMS for Telecommunications Applications" (PDF).
  2. "Purpose of Mnesia". Open-source Erlang project.
  3. "Mnesia Getting Started guide". Open-source Erlang project.
  4. "Mnesia Reference Manual (v 4.4.5)". Open-source Erlang project.
  5. "6.17 Fun Expressions". Open-source Erlang project.
  6. Gavin Terrill (20 August 2007). "Erlang's Mnesia - a distributed DBMS for highly scalable apps". InfoQ.
  7. "Mnesia performance basics". Archived from the original on 2012-12-02. Retrieved 2008-09-25.
  8. "About Erlang". Open-source Erlang project.
  9. "Erlang Public License, V 1.1". Open-source Erlang project.
  10. "ejabberd project homepage".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.