Skip to content
Ryan Lauterbach edited this page Jul 23, 2026 · 5 revisions

Guitar Tone Shootout architecture

The GTS wiki explains how the product model becomes software structure. Start with the system architecture, then follow a bounded context or delivery concern into its detailed page.

Architecture at a glance

GTS is a modular monolith with several Docker applications around one PostgreSQL database. Domain-driven design defines the language and bounded contexts. Hexagonal architecture separates ports from adapters. Onion architecture makes dependencies point towards the domain. A canonical relational model preserves ownership and consistency across HTTP requests and asynchronous work.

flowchart TB
    Product["Product model<br/>DI track, signal chains and shootout"]
    Contexts["Bounded contexts<br/>Core, Audio, T3K source and parked Video"]
    Domain["Domain model<br/>aggregates, values, rules and ports"]
    Applications["Applications<br/>web, synchronisation, orchestration and workers"]
    Adapters["Adapters<br/>HTTP, PostgreSQL, pgmq, files and source APIs"]
    Runtime["Runtime<br/>Docker Compose, nginx and Traefik"]

    Product --> Contexts
    Contexts --> Domain
    Domain --> Applications
    Applications --> Adapters
    Adapters --> Runtime
Loading

Read the architecture

  1. GTS-Technical-Architecture explains the system from product concepts to deployment.
  2. REFERENCE-ARCHITECTURE states the rules that implementation must satisfy.
  3. IMPLEMENTATION separates delivered capability from accepted target and parked work.

Detailed pages

The repository ADRs hold decision history. The development guide holds commands and operator procedures.

Current boundary

The backend model, source synchronisation, audio processing, orchestration and manifest publication exist. The public comparison experience and authenticated app workflows remain in active development. Video composition is parked and has no deployed worker.

Clone this wiki locally