Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59475

Spike: Evalute the complexity of adding a tenant component to NamespaceString

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Server Serverless 2021-08-30, Server Serverless 2021-09-06, Server Serverless 2021-09-13, Server Serverless 2021-09-20

    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.

      Attachments

        Activity

          People

            janna.golden@mongodb.com Janna Golden
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: