Forze

Forze is a Python framework for Domain-Driven Design and Hexagonal Architecture in backend services. This skill is a routing index: the reference files under references/ hold the actual material, and you read the ones a task needs.

The mental model, in four sentences

Your application declares logical specs — a DocumentSpec, a QueueSpec, a StorageSpec — that name a resource without naming any physical thing. Deps modules map those names to real backends (a Postgres table, an SQS queue, an S3 bucket) at wiring time. Handlers receive an ExecutionContext and reach infrastructure only through ports resolved from it. The runtime composes the registries, freezes them, and runs operations through the pipeline.

Everything else is a consequence of that split. If a handler mentions a table name, a bucket, or an adapter import, something has gone wrong — and most anti-patterns in these references are a version of that one mistake.

Read the bundle, not one file

Most tasks need three to five references, and reading one is usually wrong. These are procedures, not independent rules: an aggregate declared without its backend config is an app that does not start, and a handler written without the execution context is a handler that reaches for the wrong things. Start from the table below and read the whole row.

If the task is not one of these, pick from the index below — but check whether it decomposes into a row first.

Index

Foundations

Specs, deps and wiring

Domain

Reading and writing data

Events, messaging and realtime

Durable execution

Interface

Identity, tenancy and secrets

Encryption

Other planes

Testing under faults

Running in production

Reference

Docs are versioned. These links use latest (the newest release). If your app pins an older
forze minor, replace latest in the URL with that version (e.g. .../forze/0.6/...), or use
the version selector on the site.

• Forze documentation
• Quickstart
• Contracts overview