-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Multitenancy: Kerner-per-Tenant option #63
Comments
Hi! Thank you for the kind words :) I think this could lead to some hard to debug issues, because the What is your use case for having multiple kernel? |
The use case would be to be able to run the same code for different clients. The configuration (like for example DB urls) and the modules/bundles enabled could be different on a per-client basis. |
Hi
Great stuff here :) one question: would it be possible to add some sort of KernelProvider? By default it would just return the same instance, but it would open up a possibility to have multiple Kernel instances and return a specific Kernel based on an env configuration, or a request param (for example we could have a TenantKernelProvider that would ensuer each Tenant has its own Kernel).
That would also allow to have codnitional services - depending on the Tenant.
The text was updated successfully, but these errors were encountered: