dto-domain

Separate database rows from domain models in Rust by enforcing a three-layer pattern using Row, Dto, and Domain types. This architecture prevents internal state leakage and ensures explicit, validated conversions across service layers.

The best way to convert Rows to Domain types in Rust is through an intermediate Dto. Implement From<Row> for the Dto, then use TryFrom<Dto> for the Domain type to integrate validation and guard domain invariants during creation.

Prevent sensitive fields like password hashes from leaking into API responses by restricting them to the Row type only. Exclude these fields from the Dto layer entirely, ensuring they never serialize into outgoing wire formats.

Enforce domain validation when creating Rust entities from DTOs by implementing TryFrom<Dto> for the Domain type. This conversion path requires successful validation checks, optionally using the validator crate, before instantiating the domain model.

Use newtype wrappers for entity IDs in Rust domain models by creating distinct types like UserId for each entity. This prevents type confusion across service layers and ensures type-safe conversions between Row, Dto, and Domain boundaries.

Apply camelCase serialization to Rust DTOs for API responses by configuring serde attributes on the Dto struct fields. This ensures the wire format matches typical JSON API conventions while keeping the internal Rust naming idiomatic.