rust-ddd-example - GitLite

KO | EN

gitlite — search

#python #hacktoberfest #react #ai #typescript #go #golang #machine-learning #deep-learning #docker #macos #kubernetes #vue #mcp

rust-ddd-example

(★ 283)

A Domain Driven Design example application in Rust.

File Explorer

Download Latest Version (.zip)

- - main.yaml
- - dtos.rs
  - handlers.rs
  - mod.rs
  - requests.rs
- - entities.rs
  - mod.rs
  - repositories.rs
- - mod.rs
- - mod.rs
  - presenters.rs
  - prompt.rs
- main.rs
.gitignore
Cargo.lock
Cargo.toml
LICENSE
README.md

# Installation Guide

1. Get the code

git clone https://github.com/jdomenechb/rust-ddd-example

Downloads the entire project code from GitHub to your computer.

cd rust-ddd-example

Moves into the project folder you just downloaded.

2. Rust

Medium Recommended

Prerequisites

Git Needed to download the project code from GitHub.
Rust (rustup) Installing via rustup also installs cargo.

cargo run

Builds and then immediately runs the program.

✅ If cargo build finishes without errors, it worked. The executable is created under target/.

Pulled directly from this repo's README.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Rust Domain Driven Design Example

The purpose of this project is to write a simple application in Rust (2021 edition) that follows basic Domain Driven Design principles, in order to test the capabilities of the language to write applications that follow DDD.

## Running the project

Clone the repository, and run in the root of the project:

```bash
cargo run
```

A menu will appear that will guide you through the application.

## Structure

The source code is explicitly split into four of the typical DDD layers:
- **Domain** - Where the business rules of the application reside.
- **Application** - The layer that orchestrates Domain and Infrastructure, and contains the use cases for your application.
- **Infrastructure** - Contains implementations of the abstractions defined in the Domain and Application layer, and other infrastructure details. 
- **Presentation** - Defines how to present the data and defined the basic controller actions. Normally, this layer is often considered "Infrastructure", and some people prefer to separate it, whereas some people don't.

`main.rs` contains the initializations of the infrastructure implementations.

The code also contains unit testing.

## Contribution
Please, feel free to contribute asking, discussing, commenting or improving the application via Pull Requests or Issues. All type of feedback will be welcomed!

## Resources

- [What is DDD - Talk by Eric Evans](https://www.youtube.com/watch?v=pMuiVlnGqjk)
- [Domain-Driven Design Reference card - DZone](https://dzone.com/refcardz/getting-started-domain-driven?chapter=7)
- [(a.k.a. The Blue Book) Domain-Driven Design: Tackling Complexity in the Heart of Software - Eric Evans](https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215)
- [(a.k.a. The Red Book) Implementing Domain-Driven Design - Vaughn Vernon](https://www.amazon.com/Implementing-Domain-Driven-Design-Vaughn-Vernon/dp/0321834577)