Multi-Tenant SaaS Architecture: Designing Hierarchical Node Trees in MongoDB & Redis

Most traditional SaaS platforms assume a flat organization structure: an account has a single owner, several admins, and members. However, real-world organizations—such as national trade unions, fraternal orders, multi-location gyms, and collegiate clubs—operate as hierarchical trees. A national headquarters oversees regional councils, which in turn govern local chapters.

To allow instant querying of any sub-node tree without expensive recursive queries, OrgSets utilizes the Materialized Path pattern:

// MongoDB Node Document Schema
{
  "_id": ObjectId("66d0a1b2c4e5f67890123456"),
  "name": "Midwest Regional Chapter",
  "slug": "midwest-region",
  "parentId": ObjectId("66d0a0a1b2c3d4e5f6789012"), // National HQ
  "path": ",national-hq,midwest-region,",
  "depth": 1,
  "settings": {
    "duesCollectionEnabled": true,
    "votingDelegation": "REPRESENTATIVE"
  }
}

By indexing the `path` field with a prefix index, retrieving all chapters and teams under the Midwest Region requires a single index scan: ```javascript db.nodes.find({ path: /^,national-hq,midwest-region,/ }) ``` This pattern eliminates N+1 database roundtrips and scales effortlessly to tens of thousands of sub-nodes.