Question

I have looked and played around with RavenDb for a while and have started to look at MultiTenancy. Ayendes sample for multitenancy looks like this:

using(var store = new DocumentStore
{
    Url = "http://localhost:8080"
}.Initialize())
{
    store.DatabaseCommands.EnsureDatabaseExists("Brisbane");

    store.DatabaseCommands.EnsureDatabaseExists("Melbroune");
    store.DatabaseCommands.EnsureDatabaseExists("Sidney");

    using (var documentSession = store.OpenSession("Brisbane"))
    {
        documentSession.Store(new { Name = "Ayende"});
        documentSession.SaveChanges();
    }
}

I don’t know how each database is stored and hence the question: Will that work for large applications with a lot of tenants?

Answer 1

See the first and last paragraphs from the docs (v2.5 | v3.0).

RavenDB’s databases were designed with multi tenancy in mind, and are
meant to support large number of databases on a single server. In
order to do that, RavenDB will only keep the active databases open. If
you access a database for the first time, that database will be opened
and started, so the next request to that database wouldn’t have to pay
the cost of opening the database. But if a database hasn’t been
accessed for a while, RavenDB will cleanup all resources associated
with the database and close it.

That allows RavenDB to manage large numbers of databases, because at
any given time, only the active databases are actually taking
resources.

So yes it will support it and each database will be stored in a separate folder on disk.