← ClearLend build series

Phase 04 / From blueprint to code

Backend architecture.
Build the right boundaries first.

A step-by-step engineering series for ClearLend on .NET 10 and C# 14. Step 1 explains the layers and decisions; later steps will prove them with runnable code.

Step 1 complete6 steps coming soonClean Architecture · CQRS · feature folders
Explore the roadmap ↓
The engineering path
01ArchitectureLayer design · published now
02–04Foundation & modelSolution · domain · SQL · coming soon
05–06Working journeyCQRS API · Angular draft · coming soon
07Measured evidencePerformance & reliability · coming soon

Step 1 is published. Choose a chapter on the left to read it on the right. The roadmap distinguishes completed design work from implementation still to come.

Design explanation · Synthetic data · No backend yet

Step 1 · Chapter 01 / 75 min read

From blueprint to evidence, one step at a time

Phase 4 starts by making the backend architecture teachable. Only this design step is complete; implementation steps are published as a roadmap.

  1. 01

    Backend architecture and layer design

    Complete

    Outcome: A documented dependency direction, layer responsibilities and decision method.

    Acceptance: Readers can trace one draft-application rule from HTTP through application and domain to persistence, and see what remains a proposal.

  2. 02

    Runnable solution and CI

    Coming soon

    Outcome: .NET 10 solution, architectural checks, local startup and automated build.

    Acceptance: A fresh checkout builds, the API health endpoint responds and CI passes.

  3. 03

    Domain model and tests

    Coming soon

    Outcome: Draft-application aggregate, value objects, state rules and focused tests.

    Acceptance: Invalid changes are rejected by domain methods; valid draft transitions pass unit tests.

  4. 04

    Persistence and concurrency

    Coming soon

    Outcome: EF Core mappings, SQL migration, ownership-aware storage and conflict tests.

    Acceptance: A draft round-trips through SQL; stale updates fail without overwriting a newer version.

  5. 05

    CQRS API features

    Coming soon

    Outcome: Create/update commands, read queries, HTTP contracts and authorization.

    Acceptance: Authenticated requests return the documented success and failure responses in integration tests.

  6. 06

    First usable draft journey

    Coming soon

    Outcome: Angular create, edit, save and reload flow with clear states.

    Acceptance: A synthetic vetted borrower can resume their own draft; another borrower cannot see it.

  7. 07

    Measured engineering evidence

    Coming soon

    Outcome: Reproducible latency, throughput and resource baselines with justified improvements.

    Acceptance: Results include workload, environment, before/after measurements and remaining limits.

Phase 3 proposed a modular monolith, a borrower application slice, audit and outbox boundaries, SQL Server, and an Azure delivery path. Here we turn those proposals into a sequence of reviewable engineering results. The site explains decisions first. Later steps will add runnable code and report evidence from tests and measurements.

What is complete today

  • The proposed .NET 10 / C# 14 solution shape and dependency direction.
  • A decision method for Domain, Application, Infrastructure, API and Contracts.
  • One draft-application example traced through those boundaries.
  • A seven-step plan with acceptance criteria and explicit status.

What is still proposed

There is no ClearLend backend repository, SQL migration, deployed API, working borrower form or measured performance result in this phase yet. The examples below are design sketches. Each future step changes its status only after its acceptance evidence exists.

Decision to carry forward

A roadmap is credible when each step names an observable result and never confuses a design with running software.