Release plan for v4.0

[blackandred]

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.