Choosing an architecture for multiple tenant SaaS
Hi all,
I'm just about to embark on a journey of creating my first SaaS app that will consist of a webapp, an API and an identity server as 3 distinct solutions.
I'm trying to figure out which approach I want to go for where the database is concerned.
I've done a lot of reading and I feel like can quite happily get away with a single dB and relying on tenantid's to do the data filtering.
However, from what I've read I feel like the 'IDEAL' way forward would be to have 1 DB per tenant as it will allow for significantly easier maintenance in the future.
My concern is that I have no idea how much (if at all) this will pick up and be used so I'm a bit reluctant to put a lot of effort into dynamically spinning up a new DB upon registration etc.
That being said I'm keen to do things in the right way!
Would appreciate anyone's feedback or opinions on which approach to take, especially if you've been I. A similar situation before and regretted a choice or alternatively thought it was 100% the right way to go for you?
Cheers!
0 comments:
Post a Comment