Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Release plan for v4.0 #169

Closed
blackandred opened this issue Feb 5, 2022 · 0 comments
Closed

Release plan for v4.0 #169

blackandred opened this issue Feb 5, 2022 · 0 comments
Assignees
Labels
kind/release-plan Plans for a release, should be closed after a release is made.

Comments

@blackandred
Copy link
Contributor

blackandred commented Feb 5, 2022

The architecture of the solution is to be rewritten from scratch. From a monolith applications in a monolith repository we go cloud-native with a microservices architecture.

The target is to simplify and make it decoupled.

Server

The server will be rewritten in GO and provide only essential features at this time.

  • Upload/Download endpoint
  • Versions listing endpoint
  • Authorization endpoints
  • Token revoking endpoint
  • Configuration synchronization with filesystem and Kubernetes (to choose one of them by end-user)
  • Locking mechanism between replicas
  • Permissions simplified to few roles like: uploader, downloader, collectionManager, systemAdmin
  • Security features like backup windows

Client

Split into backup-maker and backup-controller.

The backup-controller is an optional piece that is scheduling backup-maker execution on different platforms like on Kubernetes, on local docker, via remote machine on ssh for example. Actually we plan to at this moment implement only Kubernetes, Docker and local shell support.

@blackandred blackandred added the kind/release-plan Plans for a release, should be closed after a release is made. label Feb 5, 2022
@blackandred blackandred self-assigned this Feb 5, 2022
@blackandred blackandred pinned this issue Feb 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/release-plan Plans for a release, should be closed after a release is made.
Projects
None yet
Development

No branches or pull requests

1 participant