Multi-client Web API Structure

Question

Multi-client Web API Structure

Asked 7 years, 6 months ago

Viewed 767 times

9

I’m in the following situation:

I have a web application that accesses the data through a C#Webapi. I need to apply the concept of multitenancy in order to allow my application to be accessed by multiple customers and for each customer to access their database individually.

Faced with this need, I researched in Sopt and found the following questions:

Web application for multiple people

Databases for different customers

As for the concept I understood, but my doubt is about deploy my Webapi and what would be the best practice:

Deploy and host a single instance of the API on IIS (and redirect access to the database via code)?

Or I should perform the Deploy individualized, ie host numerous instances of the API in IIS, each accessing its database?

In case the second option is the most viable, is there any way to make this multiple deploy more automated? Is there any cloud feature that enables this deployment scheduling (Azure, Amazon, etc...)?

Clarification - when you say 'each one accessing your database', you mean that each customer will have their data stored in unique database instances, or was just an expression (data from multiple clients in the same database)?

– OnoSendai

2017/01/03 at 13:51
@Meiaesquerda, is exactly that, each client with a unique database instance. To get an idea, currently our need is for around 100 customers.

– Julio Borges

2017/01/03 at 13:53
Its cost of maintaining the structure will be considerably higher. Also imagine that whenever you change the template the patch should be applied in 100+ instances - this is if you don’t allow banks to be in different versions of patching.

– OnoSendai

2017/01/03 at 13:54
@Meiaesquerda, really, the intention of this question is to raise what would be the best practice and what is most used or how the community acts in this type of situation.

– Julio Borges

2017/01/03 at 13:57
A question. Whenever there is an update all customers should be updated?

– Randrade

2017/01/03 at 14:41
@Randrade, here comes the famous one... Today yes all will have the same update, more can occur situations where there is something specific, the way we work today this is solved programmatically with Patterns and object orientation.

– Julio Borges

2017/01/03 at 14:47
This system uses the model Saas (Software as a Service)?

– Randrade

2017/01/03 at 14:48
@Randrade, yes, our initial idea is this.

– Julio Borges

2017/01/03 at 15:04

Show 3 more comments

1 answer

Browser other questions tagged c# database asp.net-web-api multi-tenancy

You are not signed in. Login or sign up in order to post.

by OnoSendai • **36,218** points · Answer 1 · 2017-01-03T14:14:43+00:00

The question is a little wide. I will try to provide some parameters that will help you choose your ideal scenario.

Individual databases ensure data isolation (one user of one client will not see another’s data). On the other hand, your structure maintenance cost will be considerably higher - imagine that whenever you change the model the patch should be applied in 100+ instances. This scenario becomes even more complicated if you allow banks to be in different versions of patching.
Additionally you will need a repository exclusively to provide tenancy Scope - a bank where customers and their users are registered.
A shared databases simplifies its patching process, but needs a greater effort to ensure isolation - search interfaces must at all times take into consideration the customer to which the user is associated.
To API can have its scope parameterized without the need for hundreds of deploys. Some usage policies that may be useful are definition of scope by credentials, where the scope of data to be used is set after the user’s Sign-in, or by domain, where so much cliente1.api.empresa.br when cliente2.api.empresa.br are mapped to api.empresa.br, and internally your API chooses the data scope according to the accessed subdomain (example).