3 ms·
- I love clean REST APIs so I can clearly see the value in your service over others (e.g. using S3 directly). But the benefits probably aren't immediately obvio
by delano 16y ago
- I love clean REST APIs so I can clearly see the value in your service over others (e.g. using S3 directly). But the benefits probably aren't immediately obvious to most potential customers. Maybe consider a side-by-side comparison of steps involved.
- Do you encrypt the data before storing it to S3 or store as-is? I need to think about it more but assuming you store as-is, I think I prefer that over Tarsnap's approach. You may want to consider a comparison between this service as well. (As a side note, I would be using Tarsnap right now but I'm in Canada)
- What is the need for charging for Request Processing? I guess that would prevent storing many small files, but it complicates the pricing model. It will be easier to communicate your offering if all costs are included in the data transfer and storage prices.
- mleonhard 16y agoI'm glad that you like the API. I'm working on a side-by-side comparison of RestBackup and other services. RestBackup receives the data from the customer via HTTPS and submits it to S3 also over HTTPS. So the data is encrypted in-transit but remains in S3 as-is. This is the minimum viable product. I'm considering encrypted storage as a feature for the public Beta. RestBackup has per-request charges for the same reason that S3 and CloudFiles have them: to avoid losing money on high-volume request loads on small files. If you need to store many small files, it might be more efficient to package them up in a tar archive. Thanks for the great comment and the tweet! I hope to see you in the alpha-test!