You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similarly, we could have distributed locking and a message bus implementation with SQL Server (Orchard 1 actually has that). Maybe also a Data Protection store, but I consider that less of an issue, since there are alternatives for that already (Azure Blob, and you can use the local file system too if you map it to a shared drive).
Describe alternatives you've considered
Hisham's Garnet module covers a similar aim with Garnet, but that also needs a separate service.
The text was updated successfully, but these errors were encountered:
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
Is your feature request related to a problem? Please describe.
Currently, you need Redis for multi-node hosting. This complicates the hosting infrastructure, and ideally, we wouldn't need Redis.
Describe the solution you'd like
When using SQL Server, we could also use the Distributed SQL Server Cache for distributed caching instead. Currently, that doesn't necessarily work out of the box.
Similarly, we could have distributed locking and a message bus implementation with SQL Server (Orchard 1 actually has that). Maybe also a Data Protection store, but I consider that less of an issue, since there are alternatives for that already (Azure Blob, and you can use the local file system too if you map it to a shared drive).
Describe alternatives you've considered
Hisham's Garnet module covers a similar aim with Garnet, but that also needs a separate service.
The text was updated successfully, but these errors were encountered: