[SERVER-59475] Spike: Evalute the complexity of adding a tenant component to NamespaceString Created: 20/Aug/21  Updated: 15/Sep/21  Resolved: 15/Sep/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Janna Golden
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Server Serverless 2021-08-30, Server Serverless 2021-09-06, Server Serverless 2021-09-13, Server Serverless 2021-09-20
Participants:

 Description   

Two popular approaches to supporting multi-tenancy in the server are

  1. move atlasproxy-like behavior into mongos/mongod at the service level, append tenant ids to incoming commands
  2. add a concept of tenancy to the server codebase, and ensure that server components consider tenancy as a first-class feature.

The first solution requires very few changes to the server, but may introduce a large amount of complexity at the service layer. The second solution requires a large amount of mechanical changes to the server code base, as well as a unknown impact on areas of the code where namespace are built by hand or namespaces aren't considered at all.

The goal of this spike is to evaluate the complexity of implementing the second approach.



 Comments   
Comment by Janna Golden [ 15/Sep/21 ]

Results/summary doc here.

Comment by Janna Golden [ 20/Aug/21 ]

Doc outlining the goals and proposed steps here.

Generated at Thu Feb 08 05:47:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.