Correction on the statistics: Data size per tenant could be somewhere around 35 MB (under load) and around 25000 records in a couple of tables. Other tables (around 15 in all) will have very less amount of data comparatively and there are no BLOB/CLOB type of columns in the database.
On Thursday, October 17, 2013 5:14:40 PM UTC+5:30, aditya wrote: > > Hi, > > As a part of providing multi-tenancy support to our application, I was > looking for alternatives for enhancing the current H2 database for the same. > > Couple of options that I was thinking were: > 1. same database, different schema (one schema per tenant) > 2. different DB instance per tenant > > Statistically, data size per tenant could be somewhere around 4 MB (under > normal load) and around 10000 records in a couple of tables. Other tables > (around 15 in all) will have very less amount of data comparatively and > there are no BLOB/CLOB type of columns. > > Assuming that both these options will give me good isolation of tenant > data as compared to any other option, can you suggest which of the two will > fare better in terms of overall performance and maintainability? What are > the pros and cons of these alternatives and are there any other better > options than the ones I have mentioned? > > Regards, > Aditya > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
