Hello,
I thought we are speaking of major changes in this post. Like other users said in V7 was the change of Kendo UI, in V8 the change of Configuration Tool.
We are speaking of major changes in v9, right?
In general, when suggesting features please try to focus on the problems that a feature will help solve, rather than suggest technical solutions. This applies to everyone who suggests a feature in Aware IM. It is much easier for us to understand THE PROBLEM, because then we can pick the most appropriate SOLUTION.
In earlier post I have mentioned your youtube video where Pros and Cons of both strategies are mentioned (shared database & separate BSV).
Excuse me for repeating myself "Is not my invention".In other modern frameworks this feature is used in large applications for many years now.
microsoft:
https://docs.microsoft.com/en-us/azure/sql-database/saas-tenancy-app-design-patterns
https://www.codeproject.com/Articles/848111/Multi-Tenancy-System-With-Separate-Databases-in-MV
Laravel/PHP:
https://tomschlick.com/2017/07/25/laracon-2017-multi-tenancy-talk
Pros:
Segmented data. Zero chance of customer A to see customer's B data.
Easier of long term scalability
SuperAdmin dashboard inside the shared DB (for users, licenses, notifications). Admin stuff . Please tell me how you manage Admin stuff with separate BSV's?
Portability: data is easier to export, without complex separation steps.
Backups can be doen separately per tenant, making them easier to restore.
Enterprise customers can be transitioned to on-premise setups easily
Tenant data can be easily deleted at the request of the owner.
Choose where to store a customer's data based on their location
Of course, from above, all are doable with today's architecture, minus the Admin shared part which is critical when you want to sell SaaS apps. Keeping real-time inventory of users/licenses(login data,etc) is an important part for such a business.
'Note: My wish list is simply a desire for Aware to be used by a wide range of developers and not trying to find fault in it.'
Thank you.