|
|
2 år sedan | |
|---|---|---|
| .. | ||
| include | 74cb43f8b1 fix(ds): Add unique ID to the key | 2 år sedan |
| src | 7c0d37fdb9 feat(lts): inherit previous generation's lts when possible | 2 år sedan |
| test | 7c0d37fdb9 feat(lts): inherit previous generation's lts when possible | 2 år sedan |
| BSL.txt | 8d6bcc1414 refactor(ds): emqx_replay -> emqx_durable_storage | 2 år sedan |
| IMPLEMENTATION.md | c91df2f5cd refactor(ds): Create a prototype of replication layer | 2 år sedan |
| README.md | e238602533 fix(ds): Update README | 2 år sedan |
| rebar.config | 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` | 2 år sedan |
emqx_ds is an application implementing durable storage for MQTT messages within EMQX.
Streams. Stream is an abstraction that encompasses topics, shards, different data layouts, etc. The client application must only aware of the streams.
Batching. All the API functions are batch-oriented.
Iterators. Iterators can be stored durably or transferred over network. They take relatively small space.
Support for various backends. Almost any DBMS that supports range
queries can serve as a emqx_durable_storage backend.
Builtin backend based on RocksDB.
TBD
Currently it's only used to implement persistent sessions.
In the future it can serve as a storage for retained messages or as a generic message buffering layer for the bridges.
emqx_durable_storage doesn't have any configurable parameters.
Instead, it relies on the upper-level business applications to create
a correct configuration and pass it to emqx_ds:open_db(DBName, Config)
function according to its needs.
None
TBD
Please see our contributing.md.