At first, Spaces made me too happy. I believe that it did the same for several others who aren’t happy with the high bandwidth pricing at Amazon S3. But by the passage of time, Spaces isn’t going to do what I was expecting. Initially, we don’t have the CNAME support yet which makes it impossible for us to leave Amazon S3 (where custom domains are used). Secondly, when I talked to Digital Ocean support, they say that one should not exceed the 200 requests per second limit. I know 200 requests per second is a decent limit but I am really not happy with a limit like this as my application would send much more requests than this limit in peak hours. Now I feel that although Spaces offer much lower price than S3, it isn’t an alternative of S3 at all. In terms of scalability, I see a lot of restrictions. What do you say? Any explanation from the community or the support staff will be highly appreciated. Several confusions are stopping me from migrating my data to Spaces.

  • Just an update I noticed myself - spaces now have support for CNAME. :)

  • Your problem is with interacting with the Spaces’ api? I mean, in terms of delivery to your app’s users? Is it limiting also? I’m interested, because I’m currently migrating over millions of images, but my app uses the CDNs to deliver the content to my app users.

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.

Submit an Answer
2 answers

I have found Spaces just isn’t reliable or fast enough for production use, and that is a great shame. it is perplexing why Digital Ocean haven’t made Spaces great.