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
One of the goals of this project is to provide users with a self-hostable feed service.
To achieve this, the following aspects are necessary:
Tools and echanisms for data backup and resoration
Observability
Tools and Mechanisms for Data Backup and Restoration
We want to provide these tools and mechanisms within the same release cycle as syndicationd. While it could be managed in a separate repository, having it in the same repository reduces management costs (CI, dependencies management, release cycle).
Observability
By implementing consistent OpenTelemetry signals across synd-api and kvsd, we can offer complete observability.
Issues to Resolve During the Port
The current kvsd has the follwing issues:
kvsd and CLI are in the same binary.
The kvs-client feature cannot be used independently (it also depends on kvsd).
No performance tests are avaialble.
OpenTelemetry is not instrumented.
Therefore, during the port, we plan to split kvsd into the following packages
synd_kvsd: Implementation of kvsd
synd_kvs_client: Implementation of the kvs client, which will be used by synd_api
synd_kvsctl: CLI for kvs
synd_kvsadm: Admin tool for kvsd handling tasks like backup
Goal
Manage
kvsd
within the syndicationd project.Motivation
One of the goals of this project is to provide users with a self-hostable feed service.
To achieve this, the following aspects are necessary:
Tools and Mechanisms for Data Backup and Restoration
We want to provide these tools and mechanisms within the same release cycle as syndicationd. While it could be managed in a separate repository, having it in the same repository reduces management costs (CI, dependencies management, release cycle).
Observability
By implementing consistent OpenTelemetry signals across
synd-api
andkvsd
, we can offer complete observability.Issues to Resolve During the Port
The current
kvsd
has the follwing issues:kvsd
and CLI are in the same binary.kvs-client
feature cannot be used independently (it also depends onkvsd
).Therefore, during the port, we plan to split
kvsd
into the following packagessynd_kvsd
: Implementation ofkvsd
synd_kvs_client
: Implementation of thekvs
client, which will be used bysynd_api
synd_kvsctl
: CLI forkvs
synd_kvsadm
: Admin tool forkvsd
handling tasks like backupTasks
The text was updated successfully, but these errors were encountered: