A compact Node.js backend project exploring multi-tenant authorization, service boundaries, reliable event delivery, caching, auditability, and failure handling.
The system follows one B2B access-control scenario across three focused services:
- Access Service owns organizations, memberships, roles, and authorization decisions.
- Project Service owns projects and requests tenant-scoped authorization from the Access Service.
- Audit Service consumes integration events and builds a queryable audit history.
The planned local environment uses PostgreSQL, Redis, Kafka, MongoDB, Keycloak, and Docker Compose. Each technology has a specific responsibility; the project does not assume that this level of infrastructure is necessary for every production system.
The root npm workspace and shared TypeScript foundation have been initialized. Application service implementation has not started yet.
[----------] 0%
Each filled block represents 10% of the implementation. Update the bar and percentage as the project moves forward.
- Project brief — scope, architecture, guarantees, failure scenarios, and definition of done.
- Project intent and production caveats — rationale, alternatives, and limitations of the demonstration architecture.
A reviewer should be able to run the complete environment locally, follow an allowed and a denied authorization flow, inspect the resulting events and audit data, and observe how the system behaves when selected dependencies are unavailable.