currency-tracker

A learning-by-doing currency tracker built solo with AI agents. Clean Architecture, .NET 10 LTS, Wolverine, Aspire, Postgres, Redis.

Current phase

Phase 12 — Worker + scheduled ingestion + alerts + outbox. The API is live and authenticated (auth landed in Phase 11). Phase 12 turns the Worker from a no-op host into a durable, scheduled message host: Part 1 adds the daily scheduled ingestion on a Postgres outbox/inbox; Part 2 adds the ingest → evaluate → dispatch alert cascade. The build plan runs through Phase 16 (optional React frontend). Deploy is Phase 14; ignore anything deploy-related until then.

Running locally

Phase 7 lands the Aspire AppHost. From a clean clone, one command brings up the entire local stack (Api, Worker, Postgres, Redis, and the Aspire dashboard):

dotnet run --project src/CurrencyTracker.AppHost

Prerequisites:

• .NET 10 SDK (10.0.300 or newer — see global.json).
• A Docker-compatible container runtime: Docker Desktop, OrbStack (macOS), or Docker Engine (Linux). Aspire pulls the Postgres and Redis images on first run; subsequent runs reuse the cached images and the named data volumes (currencytracker-pgdata, currencytracker-redisdata) so any seeded data survives an AppHost restart.

To wipe local data and start clean:

docker volume rm currencytracker-pgdata currencytracker-redisdata

The Worker runs the daily rate-ingestion job on a schedule (Quartz cron, 06:00 UTC by default) and publishes through a Postgres-backed Wolverine outbox; you can watch a run in the dashboard's Traces tab. Set Worker:IngestSchedule to */30 * * * * ? to see it fire every 30s.

The Aspire dashboard

After dotnet run --project src/CurrencyTracker.AppHost, the AppHost prints a dashboard URL to stdout (a randomly-assigned local port). Open it in a browser.

The Resources tab shows the running resources once everything is healthy: postgres (with currencytracker as a sub-resource), cache, api, and worker. The Traces tab shows OpenTelemetry traces in real time — hit GET /ping on the Api and the trace appears within a second. The Logs tab streams structured logs from each resource. The dashboard has no authentication and is not exposed beyond localhost; Phase 14's Azure deployment uses Application Insights instead.

Development environment

dotnet --version            # 10.0.300 or newer
csharpier --version         # global tool, used by every PR
gh auth status              # authenticated
docker info                 # container runtime running

Architecture

CurrencyTracker follows the Clean Architecture dependency direction: Domain ? Application ? Infrastructure ? (Api | Worker). Domain has zero outbound references; each layer depends only on the layers below it. Architecture tests under tests/CurrencyTracker.Architecture.Tests fail the build when the contract is violated.

flowchart LR
    %% Production-code layers
    Domain[CurrencyTracker.Domain]
    Application[CurrencyTracker.Application]
    Infrastructure[CurrencyTracker.Infrastructure]
    Api[CurrencyTracker.Api]
    Worker[CurrencyTracker.Worker]

    %% Test projects
    DomainTests[Domain.UnitTests]
    AppTests[Application.UnitTests]
    ArchTests[Architecture.Tests]

    %% Production-code reference arrows (solid; enforced by architecture tests)
    Application --> Domain
    Infrastructure --> Application
    Infrastructure --> Domain
    Api --> Infrastructure
    Api --> Application
    Api --> Domain
    Worker --> Infrastructure
    Worker --> Application
    Worker --> Domain

    %% Test ? production arrows (dashed; convention, not enforced)
    DomainTests -.-> Domain
    AppTests -.-> Application
    AppTests -.-> Domain
    ArchTests -.-> Domain
    ArchTests -.-> Application
    ArchTests -.-> Infrastructure
    ArchTests -.-> Api
    ArchTests -.-> Worker

    %% Styling: src/ blue, tests/ grey
    classDef src fill:#dbeafe,stroke:#1e3a8a,color:#0f172a
    classDef tests fill:#f1f5f9,stroke:#475569,color:#0f172a,stroke-dasharray: 5 3
    class Domain,Application,Infrastructure,Api,Worker src
    class DomainTests,AppTests,ArchTests tests

Loading

Project documents

• AGENTS.md — conventions, "Don't" list, gotchas. Read this if you are an agent session, before doing anything else.
• docs/decisions/ — architecture decision records.

Licence

Apache License 2.0 (see LICENSE).