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

Add SQL Server distributed services #16149

Open
Piedone opened this issue May 23, 2024 · 3 comments
Open

Add SQL Server distributed services #16149

Piedone opened this issue May 23, 2024 · 3 comments
Assignees
Milestone

Comments

@Piedone
Copy link
Member

Piedone commented May 23, 2024

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.

@hishamco
Copy link
Member

I might be interested in this, but for messaging we could use Azure Bus

@Piedone
Copy link
Member Author

Piedone commented May 23, 2024

That can be a solution that works for certain use cases, but this is specifically about not having to set up any further external service.

@sebastienros sebastienros added this to the 2.x milestone May 30, 2024
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants