microsoft / microsoft/durabletask-netherite

Custom backend store / queue

Open
#434 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 question
Dominant language
C#
Stars
239
Forks
37
Avg merge
1d 10h
Merged PRs (30d)
2

Description

Hello folks!

We are using durable functions outside Azure with the SQL Server backend. This has been not ideal. I see that Netherite has some abstractions in regards to both the queue and the underlying storage.

Could you guys give me a hint what exact interfaces should I implement and how to register them with Netherite so I can use those 3rd party queues/storage? I'm not expecting supports for them in the mainline but I have a peculiar scenario here which I would love to leverage Netherite whole backend and just replace the underlying queueing from EH and Az Blobs to something else.

Any advice would be appreciated.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Netherite's queue and storage abstractions and the entry points used to register them. Check whether replacing Event Hubs and Azure Blob Storage is supported through public extension points. Done means identifying the exact interfaces and registration path, or confirming that this customization is unsupported.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, sql
Domain
backend, databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.