Design for migrating to Multitenant architecture
We are in a process of redesigning our product code in such a way so as to support multitenancy.
How to deal with runtime changes to tenant-location in a clustered, multitenant web application with app-managed datasources?
I have a Java web application that supports multi-tenancy to keep customer data
separate.
How to deal with runtime changes to tenant-location in a clustered, multitenant web application with app-managed datasources?
I have a Java web application that supports multi-tenancy to keep customer data
separate.
How to deal with runtime changes to tenant-location in a clustered, multitenant web application with app-managed datasources?
I have a Java web application that supports multi-tenancy to keep customer data
separate.
How to deal with runtime changes to tenant-location in a clustered, multitenant web application with app-managed datasources?
I have a Java web application that supports multi-tenancy to keep customer data
separate.
Multi-user time based simulation – deploying new version without downtime
I am making a multiplayer strategy simulation game. The game runs in turns of fixed duration, e.g. 1 minute.
Muti-tenant Webapp Setup Defaults and Configurations
I have a multi tenant webapp. When a new tenant is created there is a bunch of defaults and configurations that need to be created in the DB for the new tenant, so of these inserts are related to each other and must happen in a specific order so I can get the ID of the related item. Here is an short version of what needs to happen
Design for a shared checkout
I am currently working on a ecommerce system that is slightly different in structure to a typical ecommerce system in that you have multiple stores, accessing the same database from different URLs.
Authorizing view content
Let’s say I have a view which should change it’s content based on the user resp. on the users permission.
Multitenancy and nested set trees
The application I work on utilizes nested sets1 to represent tree structures within our database.
We need to expand a particular area of access control to support multiple clients who should not be able to see other client’s information (aka multi-tenancy).
We have preferred the nested set approach over the more common, “naive” approach for a number of reasons as summarized in this presentation on slide 69.