Is Spaces object storage a good solution for storing website and app static assets?

I’m considering moving from AWS S3 to Digital Ocean’s Spaces but I read in the documentation something that doesn’t make much sense to me for an object storage (at least for my use case) and I hope someone could clarify things:

In the documentation it says to avoid small files (less than 1MB) and the minimum optimal file size for best performance is 20MB. However in the case of static assets for websites and apps small files is what you want to have. A good case would be if all assets in a website are smaller than 1MB. So almost 99% of the uploads my users make is image files less than 1MB.

Then my app makes thumbnails of those images to make even smaller sized images to improve performance. Less file size = more speed.

So does this make Spaces not a good solution for my use case? If I was to use Spaces how would I do that efficiently with small files. (Other than combing them into one larger file.)


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey friend,

This is a popular use case and should be fine. I recommend enabling the CDN feature with it, especially if you see a high volume of traffic. There is some rate limiting that occurs at high request levels, and the CDN feature should take care of that.