Tenant isolation is part of the domain
Clan ownership and access are modeled as first-class application concerns instead of being added around generic CRUD endpoints.
SaaS platform
COC SaaS
A backend foundation for a multi-tenant Clash of Clans management platform with role-based access and scheduled data ingestion.
ARCHITECTURE / CONCEPTUAL VIEW
Derived from public repository documentation
01Next.js Clientinterface
02NestJS APIservice
03BullMQ Workersservice
04PostgreSQLdata
05Redisinfrastructure
06CoC APIinfrastructure
CHALLENGE
What the system needed to solve.
The platform needed to keep clan data isolated while synchronizing external game data and supporting different permission levels for members and administrators.
CONSTRAINTS
The boundaries that shaped the build.
- Keep tenant data isolated across clans.
- Coordinate external API ingestion without blocking user requests.
- Support role-based access from members through super administrators.
ENGINEERING DECISIONS
Choices with consequences.
Background work leaves the request path
BullMQ and Redis create a foundation for polling and synchronization work that should not slow interactive API calls.
Contracts stay inspectable
Swagger documentation and structured modules make the backend easier to test, integrate, and extend.
RELIABILITY CONSIDERATIONS
Prepared for the operating reality.
- Database migrations support repeatable change
- Docker Compose documents service dependencies
- Queue-backed ingestion separates external API risk
OUTCOMES / HONEST EVIDENCE
What can be stated today.
- The public backend documents authentication, tenant, user, and ingestion modules.
- Approved usage metrics and production screenshots are pending.
TECHNOLOGY