Code Monkey home page Code Monkey logo

Comments (4)

jeremy avatar jeremy commented on August 27, 2024

I hear you. All the ingredients for this are coming together, if you care to combine & bake:

  1. register a custom locator for your app: #7
  2. implement in terms of a GlobalID::URI: #6
  3. support your GlobalID params using GlobalID::URI query params: needs work! 😁

from globalid.

jeremy avatar jeremy commented on August 27, 2024

❤️

On Wednesday, October 8, 2014, Kasper Timm Hansen [email protected]
wrote:

Closed #39 #39 via #44
#44.


Reply to this email directly or view it on GitHub
#39 (comment).

from globalid.

jhubert avatar jhubert commented on August 27, 2024

@jeremy I'm curious about your opinion on "app" when it comes to the concept of a GlobalID and multi-database tenancy setups.

If the GID is a hierarchy, it seems like it's descending in specificity from App, to Model, to ID, to params.

If you're in a multi-tenant setup that uses different databases (or, like in our case, different schemas) then ids for objects can increment independently as though there in entirely different apps.

Thus, User.find(1) would return different records based on the current customer.

Using params support for tenants, the gids would look like this:

gid://MyApp/User/1?tenant=customer1
gid://MyApp/User/1?tenant=customer2

But, I've been playing with that for a little while and it feels out of place in the specificity. The tenant param feels to me like metadata, when it's actually core to the context of the object. You couldn't switch over to a different customer and find the object with the other customer's gid. In the hierarchy, it might better be placed between App and Model, like App -> Tenant -> Model -> ID.

Given the current structure of GlobalID, would it make sense to have one app per tenant, like this:

gid://MyApp-customer1/User/1
gid://MyApp-customer2/User/1

Do you see any issues with that? Am I thinking about GlobalIDs wrong?

from globalid.

jeremy avatar jeremy commented on August 27, 2024

@jhubert, recommend you check out custom locator support

  • Use compound IDs that combine the tenant and model ID
  • Register a locator for your app that splits the compound ID and looks up the tenant and model separately

from globalid.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.