I haven't used a it a lot but it's been a solid endpoint for backups.
I did some medium-intensity benchmarking a while back and decided not to put certain server data on it because I was getting a few 20+ second timeouts per thousand read requests. I can handle server errors, and I have retry logic, but this was something where I needed to be able to access the data within a second or two. Maybe it would have worked better if I set a very aggressive timeout, I'm not sure. Deeper testing is something I'll worry about some other time if the data actually grows past a couple hundred gigabytes.
This was mostly with the S3 API, I don't remember if I ever succeeded in getting the program to use the native one.
I did some medium-intensity benchmarking a while back and decided not to put certain server data on it because I was getting a few 20+ second timeouts per thousand read requests. I can handle server errors, and I have retry logic, but this was something where I needed to be able to access the data within a second or two. Maybe it would have worked better if I set a very aggressive timeout, I'm not sure. Deeper testing is something I'll worry about some other time if the data actually grows past a couple hundred gigabytes.
This was mostly with the S3 API, I don't remember if I ever succeeded in getting the program to use the native one.