Abdel, Asif, welcome to the SaaS club !
May I suggest you like this post which resumes our expectations and support the corresponding youtrack ticket.
Mike
Hi all!
We are using the database per tenant approach, and we are facing some difficulties: after connected to another datastore I can save an entity, but then the display screen is not refreshing. When we did it with one db it went smoothly. So we have a list and a create button. I create another element, then it shoukd be added ti the list. I create the new element, the item is saved to the db, but the list is not refreshing.
Do you have any advice on this?
Thanks,
Attila
Hi @pfurini
I’ve been thinking of the same thing and using the third domain to access the right database. Did you ever get this scenario to work? If so I’d love to know what you did and how it performed
Thanks
John
Unfortunately that project never took off…
For less sensitive projects, the single db multi-tenancy approach is sufficient, and it will be soon supported OOB by CUBA (according to the latest roadmap).
For a multi db approach, the only (viable) option is to create multiple applications for each client, and build automation scripts for provisioning and deploying them. It’s way easier to automate everything (build a new application instance for a new client, creating a new database, configure the container behind an nginx proxy, etc) than trying to stretch the framework itself beyond its current limits.
P.
Hi @pfurini
Many thanks for your reply. I was hoping for a different response. I’m trying out the single database tenancy plugin and it seems to work fine however my data is very sensitive so the split dB approach is cleaner for clients.
Sounds like the auto build and deploy thing might work if you say it is easy 
My issue is cost. Is it possible to run multiple apps on a beefy server and if so how many can be run without killings things? Maybe you have looked at this
Well, TBH it is easy if you have a certain amount of DevOps experience, or you can “hire” it. There are several ways, and tools, to achieve even 100% automation, but it does not come for free.
For this question, I’ll give you this link to another thread: Production Requirements questions - CUBA.Platform
Unfortunately there couldn’t be THE answer to your question. Server sizing and capacity planning is one of the hardest part in every deployment strategy, and can only be estimated by considering your specific requirements (beside base ones, and that topic will give you some initial guidance).
P.
Hello to all,
I wanted to announce that I just managed to implement multitenancy in CUBA 7.2 using the TenantsRoutingDataSource Konstantin provided in combination with the multitenancy add-on. With a few lines of code (by extending an Authentication provider class) and the fact that multiple users can exist with the same login but different sysTenantId, I managed to internally multiply the users for each distinct database, so that no more limitations exist now. (taking advantage of CUBA built-in features like user filters, roles, etc. which are saved in the main db).
After user log in in the main application, it can chose which database to connect to instantly, can create databases on the fly, and all the configuration, which is stored in the main data store in tables having sysTenantId column, are related to that specific database.
So, problem solved for now. But regarding the future JMIX platform, 2 questions arise: 1. Multitenancy addon will be available in the new platform ? Hopefully yes.
2. Probably the TenantsRoutingDatasource will have to be rewritten?
Thanks, Tudor
May I get sample project.
Thanks
Umesh
I will try to make a sample project.
Hi Tudor,
- Yes, the single-database multitenancy add-on is planned for Jmix release 1.0 in June.
- Yes, because the user session mechanism in Jmix is very different from CUBA.
Regards,
Konstantin