Home

System Design Project

Multi-Mess Management Platform

A multi-tenant management system where Mess is a first-class tenant and operational context.

Architecture

Multi-Tenant

Core Context

Mess

Database

Relational

Primary Focus

Domain Design

01 — Problem

Managing a mess as a system

A mess involves members, meals, expenses, bazar, payments, monthly accounts, and different levels of responsibility. The system must keep these domains connected while maintaining historical records and separating data between different messes.

02 — Core Concept

Mess as a first-class tenant

User→MessMember→Mess→Mess-specific resources

Instead of creating a separate application or database for every mess, the platform uses a shared system where the active Mess determines the tenant and operational context.

03 — Design Principles

01

Users are global to the platform.

02

Mess is the first-class tenant and operational context.

03

Mess-specific resources belong to a Mess.

04

Membership connects users to a Mess.

05

Historical records remain after a member leaves.

04 — System Scope

Membership

Users, membership periods, roles, and mess context.

Meal Management

Daily meals, meal counts, meal configuration, and monthly tracking.

Expenses

Bazar, rent, utilities, salaries, and other mess expenses.

Accounting

Monthly charges, payments, balances, and account transactions.

Explore the system design using the sections in the project navigation.