Eclipse Community Forums: Vorto » Multi-tenancy Concept Discussions

Help

Home

Home » Eclipse Projects » Vorto » Multi-tenancy Concept Discussions

Show: Today's Messages :: Show Polls :: Message Navigator

Multi-tenancy Concept Discussions [message #1802498]

Mon, 11 February 2019 06:26

Erle Czar Mantos

Messages: 4
Registered: July 2015

Junior Member

Hi,

I want to create a forum for discussing the multi-tenancy concept of Vorto.

To start, in order to support Multi-tenancy, these are the changes I'm planning to implement in the database structure of Vorto.

Any thoughts, ideas, questions?

index.php/fa/34855/0/

Attachment: erd-vorto.png
(Size: 28.63KB, Downloaded 365 times)

[Updated on: Mon, 11 February 2019 06:29]

Report message to a moderator

Re: Multi-tenancy Concept Discussions [message #1802499 is a reply to message #1802498]

Mon, 11 February 2019 06:41

Erle Czar Mantos

Messages: 4
Registered: July 2015

Junior Member

Also, please give some thoughts on this ideas for further refinement of the multi-tenancy concept:

- There is a default tenant.The default tenant has several predefined namespaces.

- Anonymous users (non-logged in users) can see the RELEASED models of the default tenant.

- A User_Tenant (a user belonging to a tenant) can only see his own models, the RELEASED models of other users of the same tenant, and the RELEASED models of the default tenant.

- Each tenant is configured with their own authentication and authorization providers on creation time.

- Each tenant has an admin configured on creation time.

- A tenant admin can add/remove/edit the namespaces associated with his tenant.

- A tenant admin can add/remove members of his tenant.

- Each tenant can either be open, or closed.

- Members who wish to join an open tenant doesn't need to be approved by the tenant admin.

- Members who wish to join a close tenant needs the approval of the tenant admin.

Report message to a moderator

Re: Multi-tenancy Concept Discussions [message #1802569 is a reply to message #1802498]

Tue, 12 February 2019 05:22

Erle Czar Mantos

Messages: 4
Registered: July 2015

Junior Member

I decided to simplify a bit due to several factors:

1. The User table will not really hold a lot of data due to GDPR constraints, and the complexity that arises from normalizing the user and tenant relationship with a tenant_user table outweigh the redundancy of data that comes from tethering the User directly to Tenant in a one-to-many relationship.

Attachment: erd-vorto-2.png
(Size: 25.49KB, Downloaded 324 times)

[Updated on: Tue, 12 February 2019 05:23]

Report message to a moderator

Previous Topic:	Importer Plugin
Next Topic:	Is there a code generator available for KURA??

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 08:46:49 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter