[app-server] Expose custom ThreadStore injection
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
We run multiple app-server instances and need threads to be stored in a shared backend so they can be accessed consistently across instances. Examples include object storage such as Azure Blob Storage, or another externally managed database or service.
ThreadStore already provides the required abstraction, but app-server constructs it internally and exposes no dependency-injection point for embedding hosts.
Desired API example:
let storage = AppServerStorageDependencies {
thread_store: Some(Arc::new(CustomThreadStore::new(...))),
queue_store: None,
};
run_main_with_transport_options_and_storage(..., storage).await?;
Could app-server expose a process-scoped API for supplying a custom ThreadStore and optional QueueStore, while keeping the current local storage behavior as the default?
Prototype: Reference implementation: custom ThreadStore injection
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing ThreadStore abstraction and the app-server entry point run_main_with_transport_options_and_storage, then compare the proposed AppServerStorageDependencies shape with the prototype and related pull request. Done means embedding hosts can supply a custom ThreadStore and optional QueueStore while existing local storage remains the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100