usecase

To structure a Python use case with strict transaction boundaries, create a single file containing one Request subclass and one UseCase subclass, then wrap all database interactions in a single async with self.database block.

The transport-agnostic use case pattern isolates business logic in a single file pairing a Request with a UseCase class. Apply it when you need consistent application logic decoupled from specific delivery mechanisms across your codebase.

To register a new use case in the application bootstrap, add it to the setup_use_cases function with correct imports and ensure it outputs a Result object for proper discovery and execution.

A common anti-pattern when using DBGateway transaction contexts is opening multiple database sessions within a single use case. Avoid this by enforcing a single async with self.database block to maintain transactional integrity.

Yes, your use case Request class needs dataclass slots. The pattern requires Dataclass(slots=True) usage with proper type annotations to enforce memory efficiency and strict data structure definitions.