codemountains/axum-ddd-explicit-architecture
42.4
Weak · 9 November 2026
1.5k
lines of production code
Rust
primary language
7
measurements over time
What this system is
This system is a Rust-based web application for managing a todo list, featuring full CRUD operations and status tracking. It provides an API with versioned endpoints and structured error handling, backed by a PostgreSQL database that supports Japanese locale. The architecture includes a containerized development environment and a layered design separating the kernel, adapters, and use cases.
Features
Add Docker and Docker Compose configuration for local development
The project now includes a Dockerfile and docker-compose.yaml to containerize the Rust application and a PostgreSQL 16 database. Users can start the entire stack with \docker-compose up\, which handles building the Rust image, running the database, and managing volumes. The configuration also introduces a \docker-app.env\ file for containerized environment variables and updates the README with instructions for running migrations and the application within the container.
(repo-wide) · high confidence
Add full CRUD operations for todos
The application now supports creating, reading, updating, and deleting todos. The \TodoRepository\ interface has been extended with \find\, \insert\, \update\, \upsert\, and \delete\ methods, and a new \TodoStatusRepository\ has been introduced to manage todo statuses. The \TodoUseCase\ now exposes \find\_todo\, \register\_todo\, \update\_todo\, \upsert\_todo\, and \delete\_todo\ methods, enabling users to manage their todo list items.
todo-app/src/usecase, todo-kernel/src/repository · high confidence
Add status tracking and enhanced repository operations for todos
The todo-adapter now tracks a status for each todo item, introducing a new \TodoStatus\ model and repository to manage status codes and names. The \TodoRepository\ has been expanded to support filtering by status, sorting results by creation date, and performing insert, update, and upsert operations that include status information. This enables users to view, search, and manage todos with their current status.
todo-adapter · high confidence
Database containerization and SQL query files added
The database service is now containerized via a new Dockerfile that runs PostgreSQL 16-alpine with Japanese locale support. Additionally, new SQL files have been introduced: check.sql provides a query to inspect table constraints for the 'todos' table, and sample.sql inserts initial test data into the 'todos' table.
database · high confidence
Introduce Todo model with status tracking and update/upsert operations
The Todo model now includes a status field, supported by a new TodoStatus struct that tracks an ID, code, and name. Additionally, the model introduces NewTodo, UpdateTodo, and UpsertTodo structs to handle creating, updating, and upserting todo items with optional fields for title, description, and status.
todo-kernel/src/model · medium confidence
Behavioural changes
API versioning and structured error handling for Todo endpoints
The Todo API now requires an explicit version parameter (e.g., /v1/todos) to access endpoints, replacing the previous implicit routing. All Todo operations (create, read, update, delete, search) now return structured JSON error responses with specific error codes and messages, providing clearer feedback for validation and server errors.
todo-driver · high confidence
Database schema updated to support todo statuses
The database schema has been updated to include a new 'todo\_statuses' table that defines various states for todos (such as 'new', 'working', 'done', etc.). The 'todos' table now includes a 'status\_id' column that references this new table, allowing each todo to be associated with a specific status. This change replaces the previous simpler schema where todos did not have an explicit status field.
migrations · high confidence
Expanded Todo model with status tracking and update capabilities
The Todo model now includes a new TodoStatusView struct and a status field in TodoView, enabling users to track and update todo statuses. Additionally, new structs (CreateTodo, UpdateTodoView, UpsertTodoView, SearchTodoCondition) support creating, updating, upserting, and searching todos with status codes.
todo-app/src/model · medium confidence
Dependencies
Update Rust dependencies and enable resolver v2
The project updates several Rust dependencies to newer versions, including anyhow (1.0.58→1.0.86), async-trait (0.1.56→0.1.80), chrono (0.4.22→0.4.38), serde (1.0.140→1.0.203), sqlx (0.6.2→0.7.4), tokio (1.20.0→1.38.0), axum (0.5.13→0.7.5), http-body (0.4.5→1.0.0), tracing (0.1.35→0.1.40), tracing-subscriber (0.3.15→0.3.18), tower-http (0.3.4→0.5.2), thiserror (1.0.35→1.0.61), and validator (0.16.0→0.18.1). Additionally, the Cargo workspace is configured to use resolver version 2.
(dependencies) · medium confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 42 → 42 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 71 → 71 (+0.0)
- Architecture 73 → 73 (+0.0)
- Maturity 48 → 48 (+0.0)
- Readiness 28 → 28 (+0.0)
- Security 43 → 43 (+0.0)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)
Resolved (4)
- Ambiguous distinction between Update and Upsert at the repository level. Both UpdateTodo and UpsertTodo have identical properties (id, title, description, status). Without seeing the implementation, it is unclear how the repository distinguishes between 'fail if not exists' (Update) and 'insert if not exists' (Upsert). If the signatures are identical, the API surface fails to communicate the distinct intent of the operation to the caller.
- Redundant DTOs with identical signatures. UpdateTodoView and UpsertTodoView have the exact same properties and constructor signatures. In most architectures, an 'Update' implies existence (requiring ID) and 'Upsert' implies upsert logic (also requiring ID). If the business logic for update vs upsert is identical at the DTO level, these should be merged into a single ModifyTodo or TodoUpdate type to reduce maintenance surface.
- Semantic mismatch in 'find' operations. The kernel repository find takes a full TodoStatus object (entity), while the use case find_todo takes a SearchTodoCondition containing only a status_code (string). This forces the use case to perform domain logic (lookup by code) that arguably belongs in the repository or requires awkward mapping, breaking the separation of concerns.
- Type mismatch in collection definition. JsonTodoList is named as a list/collection, but its property todos is typed as a single JsonTodo (singular), and the constructor accepts a single JsonTodo. This contradicts the plural naming convention and likely causes confusion or runtime errors if multiple items are expected.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
codemountains/axum-ddd-explicit-architecture was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 9 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit a11bd081c02324224cb4ff8c30e610dead78334d — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-bb0cb800cd0f.