Our initial stack comprised of DigitalOcean's highly available block storage. These were easy to configure and attach to our droplets. They are fast, and perform exactly like any other volume on Ubuntu. The hassle of partitioning, expanding as more clients came on-board without any downtime just weren't considerations we made when we chose block storage.

Also the upfront costs of block storage where we were paying for unused storage. Within the first three months we began testing Amazon S3's object storage as our storage platform for all our media and document files. It was performant without any noticeable slowness in the loading of the websites.

We experimented with DigitalOcean's Spaces, their version of object storage. We were part of their beta roll-out. After some experimentation and attempts, and constantly failing to understand how to enable CORS on the buckets we gave up on Spaces. DigitalOcean were having some uptime issues with spaces as well at the time as part of the beta roll-out.

Amazon S3 was established, proven, and resided on a separate cloud platform that could foreseeable be used as a secondary backup solution.

Taking nothing away from Space's. We are certain with some determination on our part and patience on the final roll-out all the kinks would have been worked out. We were ready to migrate, had the resources at the time to do so, and a secondary cloud solution made sense for us. Please don't allow our comments on Space's take anything away from the great folks at DigitalOcean.

Bonus discovery. Enabling Amazon's AWS CloudFront was a matter of a few clicks and all the data stored on the S3 buckets were now cached and served from the geographically closest point of presence to the visitor.

results matching ""

    No results matching ""