general-patterns

Multi-tenancy isolation works by ensuring all repository queries are explicitly tenant-scoped before execution. This pattern enforces tenancy-scoped repository queries across backend services to prevent tenant isolation gaps and data leakage.

Standardized error handling uses error code categories and a uniform response format where infrastructure errors map to INF_* codes with monitoring alerts. This enforces consistent error responses and business rules to throw domain exceptions across services.

Event-driven side effects are implemented by designing atomic use-case pipelines that trigger events upon completion. This pattern provides guidance for event-driven flows alongside multi-tenancy scoping and operational anti-patterns to avoid.

Yes, these language-agnostic backend patterns are applicable to Java and Rust, as well as NestJS and Go. They provide implementation examples for standardized error handling and architecture enforcement across all four technology stacks.

Auditing a backend codebase involves checking for layer violations, missing tenant scoping in repository queries, and inconsistent error codes. This skill provides the rules to verify that business rules throw domain exceptions and infrastructure errors map correctly.