New answers tagged

0

I would try to limit how far the concept of tenancy spreads throughout the application design. Many (micro)services can be designed without the need to have a tenantID. They may not need to know this information or whatever information is needed for them to process the task can be included in the message. For example a PDF conversion service may not need ...


1

First choice is better for security and independence between tenants, like the choice about database.But you have to build tools to handle it. Failure of one queue, don't expose failure to other tenants. First is not simple technically, but have functionals advantages : limited failure independence between tenants/confidentiality, eg: data cannot be ...


1

There is no silver bullet in this scenario, but you have to evaluate a solution for each customization aspect that you have to face in time, trying to keep separate the core api from customized services If customers just need to extend the information associated to some resource (company, user, asset) the most flexible solution is the introduction of ...


0

I think it's good that you are seeing the requirement because there will be a large, profitable customer base who will only buy your product if it can be reasonably integrated with the dozens if not hundreds of systems they already operate. Don't hack this though, think about sustainable ways to store user data with your data. A simple solution is to have a ...


2

I agree with Robert H. that there is an overarching problem here with terminology. Your customer is not using the terminology consistently or correctly, so any requirements discussions using that terminology will be problematic. Steer away from it. Instead, talk about use cases. The requirement could potentially be restated in plain terms as follows: As ...


2

In short Yes this can make sense, for example in combination with SSO, but it weakens the independence of the tenants. More infos In principle, in a multi-tenant architecture, you want each tenant to be independent of the others, as-if it would be separate system. This means that each tenant should have its own user management. However, some users ...


Top 50 recent answers are included