05-12-2016, 02:42 AM
Hi Brian,
Yes, totally agree, Database/tables are cheap - although time less so - so my “multi-tenancy” was a suggested enhancement, as will would allow anyone developing and hosting solutions to potentially only have to install and maintain/patch one installation of Userspice, instead of several or more. That said, with the separation of Userspice into Standard and Pro version, required patches will be less frequent in your Standard version.
My suggestion came from the system I'm developing (utilising UserSpice) as my original thought was to have a separate application (and Userspice) database for each client installation (which definitely has advantages in total data separation etc) but could see the advantage of having one application database in terms of deploying application fixes, patches, enhancements and new releases across multiple installation etc.
As with any suggestion, one mans meat is another mans poison, so depends on if this would be of benefit to your general client base.
Regards
Jamie
Yes, totally agree, Database/tables are cheap - although time less so - so my “multi-tenancy” was a suggested enhancement, as will would allow anyone developing and hosting solutions to potentially only have to install and maintain/patch one installation of Userspice, instead of several or more. That said, with the separation of Userspice into Standard and Pro version, required patches will be less frequent in your Standard version.
My suggestion came from the system I'm developing (utilising UserSpice) as my original thought was to have a separate application (and Userspice) database for each client installation (which definitely has advantages in total data separation etc) but could see the advantage of having one application database in terms of deploying application fixes, patches, enhancements and new releases across multiple installation etc.
As with any suggestion, one mans meat is another mans poison, so depends on if this would be of benefit to your general client base.
Regards
Jamie