Native model
Add interoperability on the top of serialization formats like bincode, postcard etc.
See concepts for more details.
Goals
- Interoperability: Allows different applications to work together, even if they are using different versions of the data model.
- Data Consistency: Ensure that we process the data expected model.
- Flexibility: You can use any serialization format you want. More details here.
- Performance: A minimal overhead (encode: ~20 ns, decode: ~40 ps). More details here.
Usage
Application 1 (DotV1) Application 2 (DotV1 and DotV2)
| |
Encode DotV1 |--------------------------------> | Decode DotV1 to DotV2
| | Modify DotV2
Decode DotV1 | <--------------------------------| Encode DotV2 back to DotV1
| |
use native_model;
use ;
;
// Application 1
let dot = DotV1;
let bytes = encode.unwrap;
// Application 1 sends bytes to Application 2.
// Application 2
// We are able to decode the bytes directly into a new type DotV2 (upgrade).
let = .unwrap;
assert_eq!;
dot.name = "Dot".to_string;
dot.x = 5;
// For interoperability, we encode the data with the version compatible with Application 1 (downgrade).
let bytes = encode_downgrade.unwrap;
// Application 2 sends bytes to Application 1.
// Application 1
let = .unwrap;
assert_eq!;
- Full example here.
Serialization format
You can use default serialization formats via the feature flags, like:
[]
= { = "0.1", = ["bincode_2"] }
Each feature flag corresponds to a specific minor version of the serialization format. In order to avoid breaking changes, the default serialization format is the oldest one.
bincode_1_3: bincode v1.3 (default)bincode_2: bincode v2.0.0-rc3postcard_1_0: postcard v1.0rpm_serde_1_3: rmp-serde v1.3
Custom serialization format
Define a struct with the name you want. This struct must implement native_model::Encode and native_model::Decode traits.
Full examples:
Others examples, see the default implementations:
Notice
native_model provides implementations that rely on metadata-less formats and serde.
There are known issues with some serde advanced features such as:
#[serde(flatten)]#[serde(skip)]#[serde(skip_deserializing)]#[serde(skip_serializing)]#[serde(skip_serializing_if = "path")]#[serde(tag = "...")]#[serde(untagged)]
Or types implementing similar strategies such as serde_json::Value.
The rmp-serde serialization format can optionally support them serializing structs as maps, the RmpSerdeNamed struct is provided to support this use-case.
Data model
Define your model using the macro native_model.
Attributes:
id = u32: The unique identifier of the model.version = u32: The version of the model.with = type: The serialization format that you use for the Encode/Decode implementation. Setup here.from = type: Optional, the previous version of the model.type: The previous version of the model that you use for the From implementation.
try_from = (type, error): Optional, the previous version of the model with error handling.type: The previous version of the model that you use for the TryFrom implementation.error: The error type that you use for the TryFrom implementation.
use native_model;
use ;
;
// Implement the conversion between versions From<DotV1> for DotV2 and From<DotV2> for DotV1.
// Implement the conversion between versions From<DotV2> for DotV3 and From<DotV3> for DotV2.
Codecs
native_model comes with several optional built-in serializer features available:
-
- This is the default codec.
- Warning: This codec may not work with all serde-derived types.
-
- Enable the
bincode_2feature and use thenative_model::bincode_2::Bincodeattribute to havenative_dbuse this crate for serializing & deserializing. - Warning: This codec may not work with all serde-derived types.
- Enable the
-
- Enable the
postcard_1_0feature and use thenative_model::postcard_1_0::PostCardattribute. - Warning: This codec may not work with all serde-derived types.
- Enable the
-
- Enable the
rmp_serde_1_3feature and use thenative_model::rmp_serde_1_3::RmpSerdeattribute.
- Enable the
Codec example:
As example, to use rmp-serde:
- In your project's
Cargo.tomlfile, enable thermp_serde_1_3feature for thenative_modeldependency.- Be sure to check
crates.iofor the most recentnative_modelversion number.
- Be sure to check
[]
= { = "1.0", = [ "derive" ] }
= { = "0.4", = [ "rmp_serde_1_3" ] }
- Assign the
rmp_serde_1_3codec to yourstructusing thewithattribute:
use native_model;
Additional reading
You may also want to check out David Koloski's Rust serialization benchmarks for help selecting the codec (i.e. bincode_1_3, rmp_serde_1_3, etc.) that's best for your project.
Status
Early development. Not ready for production.
Concepts
In order to understand how the native model works, you need to understand the following concepts.
- Identity(
id): The identity is the unique identifier of the model. It is used to identify the model and prevent to decode a model into the wrong Rust type. - Version(
version) The version is the version of the model. It is used to check the compatibility between two models. - Encode: The encode is the process of converting a model into a byte array.
- Decode: The decode is the process of converting a byte array into a model.
- Downgrade: The downgrade is the process of converting a model into a previous version of the model.
- Upgrade: The upgrade is the process of converting a model into a newer version of the model.
Under the hood, the native model is a thin wrapper around serialized data. The id and the version are twice encoded with a little_endian::U32. That represents 8 bytes, that are added at the beginning of the data.
+------------------+------------------+------------------------------------+
| ID (4 bytes) | Version (4 bytes)| Data (indeterminate-length bytes) |
+------------------+------------------+------------------------------------+
Full example here.
Performance
Native model has been designed to have a minimal and constant overhead. That means that the overhead is the same whatever the size of the data. Under the hood we use the zerocopy crate to avoid unnecessary copies.
👉 To know the total time of the encode/decode, you need to add the time of your serialization format.
Resume:
- Encode: ~20 ns
- Decode: ~40 ps
| data size | encode time (ns) | decode time (ps) |
|---|---|---|
| 1 B | 19.769 ns - 20.154 ns | 40.526 ps - 40.617 ps |
| 1 KiB | 19.597 ns - 19.971 ns | 40.534 ps - 40.633 ps |
| 1 MiB | 19.662 ns - 19.910 ns | 40.508 ps - 40.632 ps |
| 10 MiB | 19.591 ns - 19.980 ns | 40.504 ps - 40.605 ps |
| 100 MiB | 19.669 ns - 19.867 ns | 40.520 ps - 40.644 ps |
Benchmark of the native model overhead here.