MultiTenant application challenges and suggestions

[agriffard]

I am currently trying to reply to a Request For Proposal for a customer that wants to implement a tool and make it available for multiple companies through a Saas offer.

The needs are a bit challenging because they expect to reach more than 2 000 tenants with an average number of users of a few thousands per tenant.
The load peak of connections could be not too high but potentially limited on a short period (ex: 50-60 days).

Sorry, I can't go further into the details for confidentiality reasons.

I am evaluating different approaches between Custom development, and other use of libraries/frameworks like ABP, Finbuckle.MultiTenant, Mellon.MultiTenant and, of course, Orchard Core.

Orchard Core could fit and have some benefits to respond to some of the expected features:

• Multitenancy
• Localization
• Media storage
• Audit trail
• Users/Roles
• Template
• Branding (Theme, Settings)
• Api
• Recipe (Setup, Import)
• Workflow

Is there anyone that has successfully implemented a MultiTenant application with such high expectations and can share some of their experience (Challenges, ...)?

[Piedone]

Not exactly this, since we have more tenants but with less traffic on average, but DotNest is something simialr. Pretty much all the challenges we faced is now either fixed/implemented in OC or Azure, or is covered by one of our hosting modules: https://dotnest.com/knowledge-base/topics/lombiq-hosting-suite Also see https://dotnest.com/knowledge-base/topics/security and https://dotnest.com/knowledge-base/topics/managed-by-dotnest-orchard-core.

Due to the mentioned average sites, we put all of them into a single DB (with prefixed tables). This is an Azure SQL DB though, so it can grow huge (within SQL Server limites) as well as the underlying hardware's performance can be scaled up a lot. This is also cost-efficient in that unless all sites are busy at the same time, which is improbable, we have capacity to spare, but only for the whole platform, that can be used any time by certain sites spiking. Azure elastic pools can offer a similar benefit, but with a more complex hosting approach.

In other hosting environments, or if e.g. you need more data segregation due to compliance reasons, you may want to go with separate DBs.

With Media storage, it's a similar story.

BTW let me know if you'd like to collaborate on that RFP.