vh/rest-server
1
0
Fork 0
mirror of https://github.com/restic/rest-server.git synced 2026-09-26 05:51:24 -07:00
Code Issues Actions Packages Projects Releases Wiki Activity

README.md: document why and when to use rest-server

Browse Source
This commit is contained in:
Zlatko Čalušić
2017-06-04 12:10:11 +02:00
parent 907801c8b9
commit d54a589176
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+14
View File
@@ -82,6 +82,20 @@ and via HTTP, even simultaneously.
To learn how to use restic backup client with REST backend, please consult [restic To learn how to use restic backup client with REST backend, please consult [restic
manual](https://restic.readthedocs.io/en/latest/manual.html#rest-server). manual](https://restic.readthedocs.io/en/latest/manual.html#rest-server).
## Why use Rest Server?
Compared to the SFTP backend, the REST backend has better performance, especially so if you can skip additional crypto
overhead by using plain HTTP transport (restic already properly encrypts all data it sends, so using HTTPS is mostly
about authentication).
But, even if you use HTTPS transport, the REST protocol should be faster and more scalable, due to some inefficiencies
of the SFTP protocol (everything needs to be transferred in chunks of 32 KiB at most, each packet needs to be
acknowledged by the server).
Finally, the Rest Server implementation is really simple and as such could be used on the low-end devices, no problem.
Also, in some cases, for example behind corporate firewalls, HTTP/S might be the only protocol allowed. Here too REST
backend might be the perfect option for your backup needs.
## Contributors ## Contributors
Contributors are welcome, just open a new issue / pull request. Contributors are welcome, just open a new issue / pull request.