KissthePlan — API
NestJS backend of the KissthePlan wedding SaaS: shared access resolution (owner/collaborator) in the JWT, and a mapping layer that decouples the MongoDB schema from what the frontend consumes.
Infrastructure & Backend
The Challenge
A wedding can have up to 3 people managing it at the same time. The backend needed to resolve who can access which wedding without the rest of the system having to distinguish between owner and collaborator in each query.
The Solution
The authentication layer resolves at the moment whether the requester is the wedding owner or an accepted collaborator, without the rest of the API having to distinguish between the two. Joining a wedding can be done by invitation with a unique link, or with an account created directly by the organizer. Mongo data does not always match what the frontend needs, so there is an explicit translation layer between the two, field by field.
Related project
KissthePlan
Role in the project
Solutions Architect and Full Stack Dev.