Just in case you need a quick recap, a muti-tenant web application is one that can cater to multiple (but completely seperate) audiences, simultaneously. Each seperate audience is called a
tenant. To to all intense and purposes, each tenant is just a collection of users who are using the application "unaware" of the other tenants who's users are also doing the same.
A multi-tenant application is essentially an application that splits itself into multiple applications - one for each tenant - so that one Tenant can have a completely different
view of the world than another.
Now that we are all caught up, let's get down to business!
But wait.. Why would I want this?
Some indicators as to why you might want multi-tenancy are that, for certain audiences, you might want to:
- Display a different branding / appearance.
- Have different functionality enabled or disabled.
- Have different content or files accessible.
For example one tenant could look like this:
Whilst the other is simultaneously looking like this:
For the sake of this series we will be using a couple of ficticious tenants:
What are we going to cover?
During this series, I will take you through the following, starting with basic stuff like tenant resolution, and slowly adding more advanced features. However it would help if you already have a good understanding of:
1. The Middleware Pipeline. 2. DI Containers.
For a high level view of the sort of architecture we will be exploring, here is a quick diagram of he type of architecture that
dotnettency allows you to easily setup within your application:
Notice that you can achieve multiple layers of isloation (all of which are ofcourse optional) depending upon your needs. You can isolate things both at a tenant level, and at an individual module level, whilst ensuring that your host application will always behave a certain way by default.
Isolation, Isolation, Isolation - but optional.
Dotnettency's approach as a multi-tenancy library is to allow you to use as much, or as little isolation as you require. For example you can choose to do any of these:
- Isolate each tenant from other tenants (you dont have to)
- Isolate modules from other modules. (you don't have to, and could do this with some modules and not others)
- Isolate a tenants view of the host file system, from other tenants (i.e so one tenants files can not conflict with another tenants files - even though they might use the same paths. )
Before I go any further I would like to mention Ben Foster's wonderful
saaskit library which was a big inspiration for many of the features in
dotnettency and I would highly recommend you read Ben's blog - after mine, ofcourse ;-)
Ok so what is this tutorial series going to look like?
We will be creating a basic asp.net core website (from the starting template) and then enhancing with one multi-tenancy feature at a time, provided by
dotnettency, so that our site:
- Has multiple tenants (Gicrosoft and Moogle) and we can distguish between them.
- Has a null (default) tenant enabled (or disabled - thats up to you)
- Allows each Tenant to have it's own isolated
Gicrosoft's services can be isolated from
Moogleservices. Think of this if you want each tenant to be able to configure which
IPaymentProviderthey will use or something similar.
- Allows each Tenant to have it's own Middleware Pipeline - so
Gicrosoft's can have
Welcome Pagemiddleware enabled for example, where as
Mooglewill have no such middleware enabled.
- We will allow each Tenant to have its own
View of the worldin terms of file access. (i.e so that
Mooglecan't interfere with each other files, or overwrite system level files (but could optionally
overridethe system level files with their own version of the file, keeping the same path)
- Modules. We will discuss
dotnettencys concept of Modules. Modules can be enabled at the application or for particular tenants. Right now, these come in two flavours:
- Shared (or Library) Modules: These provide services or middleware. They can be added at the application level (so will impact all tenants) or on a per tenant basis.
- Routed Modules: Modules that have their own isolated container that will be restored during the request when they are routed too. Routed Modules are so called because they must have routes registered with the asp.net core routing system. Dotnettency makes it really easy. If you are developing an extension for your application that has MVC Controllers, then this would be an example of a
Routed Module. Dotnettency does not tie your module to a particular technology - you could have a mixture
Nancybased modules running for a particular tenant.
At the end of this tutorial, you will have a multi-tenant, modular & extensible application to serve as a good basis for developing your next multi-tenant capable web application.
If there is anything else you would like me to cover, please let me know in the comments.
In the meantime, if you would like to check out
dotnettency and run the samples etc, feel free -it's on Github