Hi - I am evaluating backendless as the host for converting a legacy app to a SaaS basis. The legacy app is a serious-scale system used either by agencies or corporates. My research so far suggests that backendless could be viable.
Can you give me a link to documentation explaining the best approach to single- and multi-tenant config?
Thanks in advance.
VW.
Hello @VanquishedWombat,
Welcome to our community!
We don’t have such a doc, but basically, the database can contain multiple tables, a separate one for every tenant. There is a benefit for that approach since all registered users of your app (regardless of the company/group they belong to) would be in the same place (the Users table).
Data isolation can be done by applying security with custom API keys/roles . When you have a separate table for each tenant, you can configure it so that only users in a specific role can work with data from that table.
Of course, an alternative approach would be to have a separate app for each tenant.
Regards,
Stanislaw
Thank you Stanislaw.
Can I ask a follow-on question regarding your point that
an alternative approach would be to have a separate app for each tenant.
Would the software side of the app be the same for all users?
What I am looking for here is that if I have say 50 tenants, meaning 50 separate apps, and I want to roll out a change, can my release process be automated so that all 50 tenant apps receive the change at the same time. Or must I apply the same change to all 500 individually (obviously less desirable!).
Thanks.
VW.
can my release process be automated so that all 50 tenant apps receive the change at the same time
Unfortunately, no. In your case, it’s better to use a single app.
Regards
Ok thanks.