Ecto 2.X adapter for Mnesia Erlang term database. In most cases it can be used as drop-in replacement for other adapters.
Supported features:
- Compatible
Ecto.RepoAPI. - Automatically converts
Ecto.Querystructs to Erlangmatch_spec. - Emulated
query.selectandquery.order_bys,select .. in [..]. (Emulating is slow for any large dataset,O(n * log n).) - Auto-generated (via sequence table)
:idprimary keys. - Migrations and database setup via
Ecto.Migrations. - Transactions.
- Secondary indexes.
Planned features:
- Native primary key and unique index constraints.
- Custom primary keys.
- Other transactional contexts.
Not supported features (create issue and vote if you need them):
- Type casting. Mnesia can store any data in any field, including strings, numbers, atoms, tuples, floats or even PID's. All types in your migrations will be silently ignored.
- Mnesia clustering and auto-clustering.
- Lookups in
jsonfields. - Schemaless queries.
- Composite primary keys.
- Unique/all other constraints (including associations).
- JOINs.
- min, max, avg and other aggregation functions.
- Intervals.
In general. This adapter is still not passing all Ecto integration tests and in active development. But it already can be helpful in simple use-cases.
We have a production task that needs low read-latency database and our data fits in RAM, so Mnesia is the best choice: it's part of OTP, shares same space as our app does, work fast in RAM and supports transactions (it's critical for fintech projects).
Why do we need an adapter? We don't want to lock us to any specific database, since requirements can change. Ecto allows to switch databases by simply modifying the config, and we might want to go back to Postres or another DB.
If you use Mnesia - you either get a distributed system from day one or a single node with low availability. Very few people really want any of that options. Specifically Mnesia it's neither an AP, nor a CP database; requires you to handle network partitions (split brains) manually; has much less documentation available compared to a more common databases (like PostgreSQL).
Please, pick your tools wisely and think through how you would use them in production.
config :ecto_mnesia,
host: {:system, :atom, "MNESIA_HOST", Kernel.node()},
storage_type: {:system, :atom, "MNESIA_STORAGE_TYPE", :disc_copies}
config :mnesia,
dir: 'priv/data/mnesia' # Make sure this directory existsNotice that {:system, [TYPE], ENV_NAME, default_value} tuples can be replaced with any raw values.
They tell adapter to read configuration from environment in run-time, so you will be able to set MNESIA_HOST and MNESIA_STORAGE_TYPE environment variables, which is very useful when you releasing app in production and don't want to rebuild all code on each config change.
If you want to know more how this tool works take look at Confex package.
:disc_copies- store data in both RAM and on disc. Recommended value for most cases.:ram_copies- store data only in RAM. Data will be lost on node restart. Useful when working with large datasets that don't need to be persisted.:disc_only_copies- store data only on disc. This will limit database size to 2GB and affect adapter performance.
In migrations you can select which kind of table you want to use:
create_if_not_exists table(:my_table, engine: :set) do
# ...
endSupported types:
:set- expected your records to have at least one unique primary key that should be in first column.:ordered_set- default type. Same as:set, but Mnesia will store data in a table will be ordered by primary key.:bag- expected all records to be unique, but no primary key is required. (Internally, it will use first field as a primary key).
Ordered set comes in a cost of increased complexity of write operations:
Set
| Operation | Average | Worst Case |
|---|---|---|
| Space | O(n) | O(n) |
| Search | O(1) | O(n) |
| Insert | O(1) | O(n) |
| Delete | O(1) | O(n) |
Ordered Set
| Operation | Average | Worst Case |
|---|---|---|
| Space | O(n) | O(n) |
| Search | O(log n) | O(n) |
| Insert | O(log n) | O(n) |
| Delete | O(log n) | O(n) |
It is available in Hex, the package can be installed as:
- Add
ecto_mnesiato your list of dependencies inmix.exs:
def deps do
[{:ecto_mnesia, "~> 0.9.0"}]
end- Ensure
ecto_mnesiais started before your application:
def application do
[applications: [:ecto_mnesia]]
end- Use
EctoMnesia.Adapteras yourEcto.Repoadapter:
config :my_app, MyRepo,
adapter: EctoMnesia.Adapter- Optionally set custom Mnesia data dir (don't forget to create it):
config :mnesia, :dir, 'priv/data/mnesia'The docs can be found at https://hexdocs.pm/ecto_mnesia.
We want to thank meh for his Amnesia package that helped a lot in initial Mnesia investigations. Some pieces of code was copied from his repo.
Also big thanks to josevalim for Elixir, Ecto and active help while this adapter was developed.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent