architecture-reviewer

To prevent cross-tenant data leakage, you must verify that every MongoDB query and endpoint is properly scoped by a tenant identifier like liga_id. Architectural review checks isolation boundaries across queries, middleware, and route definitions to ensure no unauthorized cross-tenant access occurs.

Financial correctness review assesses idempotency, audit trail coverage, session validation, and transaction safety in Node.js applications. It evaluates point rounding rules and database transaction handling to reduce the risk of irreversible financial bugs and data inconsistencies.

The best way to implement cache invalidation for a multi-tenant API is to use TTL-based caches keyed per league or tenant, ensuring they are invalidated on writes. Architectural review validates that caching layers maintain TTLs and proper invalidation triggers to prevent stale data.

Yes, you can use Vanilla JavaScript ES-modules for frontend SPA initialization, and architectural validation confirms this pattern. It checks frontend initialization strategies to ensure compatible ES-module patterns are used and prevents accidental inclusion of incompatible frameworks.

To review API consistency, you check whether endpoints follow standardized apiResponse and error handling patterns across the Express application. Architectural review analyzes route definitions to ensure uniform response structures, error codes, and middleware behavior throughout the API.

You need to check module activation logic when dynamic modules are introduced to a multi-tenant architecture, ensuring they are correctly activated per league. Architectural review assesses whether dynamic modules are truly isolated and not confused across fundamentally different module types.