Skip to content

Independent R&D project · Cologne

Implementation Profiles

Four technology stacks, each mapped onto the same properties.

Non-normative

Companion version
1.0
Maps to COADF Core
2.2
Status
Current
Last reviewed

Each profile maps the same architectural properties onto one technology stack, with its failure modes, verification, alternatives, trade-offs and limitations. No stack is required by COADF.

  • Illustrative reference examples

    Python and FastAPI

    A modular monolith with typed boundaries, import contracts, an append-only trail in PostgreSQL and policy as data, with tested reference examples.

    Profile version
    1.0
  • Illustrative reference examples

    Cloud-Native and Kubernetes

    Deployment boundaries, admission, network isolation, configuration provenance and release controls, with validated reference examples.

    Profile version
    1.0
  • Code examples follow in a later revision.

    Java and Spring

    Sealed types, Bean Validation, Micrometer, Spring Modulith and ArchUnit, and where a declared property stops applying.

    Profile version
    1.0
  • Code examples follow in a later revision.

    TypeScript and Node

    Runtime schemas as the source of types, framework validation defaults, AsyncLocalStorage and dependency rules.

    Profile version
    1.0

COADF Engineering Companion 1.0 · non-normative · maps to COADF Core 2.2

Publication rights reserved. No public licence is granted for the COADF Engineering Companion 1.0 or its reference examples at this time.

IP and publication status