numberz wrote:
My understanding is that the REASONS for this entire thread was two-fold, price and security.
1) Price:
Is it feasible to have a SAAS subscription for, say, $39 to $59/month?
2) Security:
I think that I can rule out the need for "medical or government grade" type security...but ultimately, if stuff does happen...would it be rather painless to get a customer up and running quickly with this method?
No, thats not the REASONS for the entire thread.
It was a discussion of physical structure of your database(s) in a multi-tenant SAAS solution:
Do you have a "Tenant/Owner" column in your tables (the original way)(co-mingled)(Aware has video on how to do a multi-tenant setup)
vs.
Using a separate BSV/set of data tables per tenant (not co-mingled) and how to manage rolling out a new BSV/database automatically.
Since 8.4, Aware has integrated a way to create a new BSV when signing up a new customer. So this simplifies creating new BSVs.
ACDC brought up the fact that once you start duplicating your BSV (redundancy) and making little tweaks here and there for customers you are on a Highway to Hell (hehe, anyone see what i did there?). This is true for many development languages so not really unique to Aware - but still a pain. At least if you had all clients PHYSICALLY on the same BSV you don't have to manage 50 different ones.
I think if it were possible to have a Dynamic Connection String that allowed users to log in to a central dispatch BSV, and then set your connection path after Login, then 1 BSV could be used with USER DATA being physically in separate tables.