Sipke Schoorstra

Thanks for the details + repro!

Elsa 3 has mastered this logic flawlessly. You might consider backporting the logic from there and submitting a pull request.

Yes, the abstraction of the persistence layer—encompassing EF Core, MongoDB, Dapper, and possible third-party implementations—makes handling this from the application layer quite practical, but the downside is the lack of...

I agree, we should untangle this 👍🏻

For most components, yes. For example, Quartz.NET requires to be configured using a persistent store in order for it to start jobs only one one node, instead of all nodes....

TODO: Add support for DB connection pooling with tenants: https://learn.microsoft.com/en-us/ef/core/performance/advanced-performance-topics?tabs=with-di%2Cexpression-api-with-constant#managing-state-in-pooled-contexts

> TODO: Add support for DB connection pooling with tenants: > > https://learn.microsoft.com/en-us/ef/core/performance/advanced-performance-topics?tabs=with-di%2Cexpression-api-with-constant#managing-state-in-pooled-contexts Actually, the `Store` utility class used internally already handles application of the current Tenant ID, rendering the...

Feedback: - Add a little architectural documentation about how multi-tenancy works in terms of security on various levels. - Do we add tenant ID to the message properties (e.g., ASB...

Hi @Itzalive Thank you for trying out the feature so early and for offering your concern. The mediator handler should have the same context as the code that fires the...

Converted PR to Draft mode because I'm merging in #5444. Once #5444 merges into main, I'll do another update of main into this PR.