Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding some API for tenant-aware services #1416

Open
dmytro-kashcheiev opened this issue Nov 8, 2021 · 0 comments
Open

Consider adding some API for tenant-aware services #1416

dmytro-kashcheiev opened this issue Nov 8, 2021 · 0 comments
Assignees

Comments

@dmytro-kashcheiev
Copy link
Collaborator

In a multi-tenant environment most likely some of the non Spine services will be multi-tenant as well. Currently, there is no way to easily implement a custom tenant-aware service. As result all calls to such services start to look multitenantService.doSomething(TenantId id .... ). In addition, it's impossible to access tenantId before the signal handler method as result all these tenant-based calls moved inside signal handlers and get them dirty and more complex.

The simplest and strict forward solution from the developer's point of view can be achieved by expanding the API of Repository.configure(Entity) to configure(TenantId, Entity). Such API will provide the possibility to correctly configure tenant-aware service before injecting it into the entity. Consider adding some API for custom multi-tenant services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants