Storj compared to Century Link Object Storage

Storj
Versus
Century Link Object Storage

Features

Storage Features of Storj compared to Century Link Object Storage
StorjFeaturesCentury Link Object Storage
Cloud based
GDPR Compliant
On premise
Open source
Versioned files
Cross Region Replication
API
S3 Compatible API
CLI, self-hosted s3 REST apiManagement interfacesPortal, REST api
Event hooks/pubsub
SLA
Maximum object filesize
Minimum object filesize
Recommended max file count per bucket
Max filesize for a bucket
300Maximum amount of buckets
Logs
Authentication / ACL
CDN integration
Peering & interconnectCenturylink/Lumen is a backbone provider for large parts of the globe
Unsupported Paid Feature Supported Unknown

Descriptions


Storj


Second-generation Cloud Storage Provider Storj, previously known as Tardigrade.io is a second-generation cloud storage provider, not unlike Filebase. Actually, it’s the other way around… Filebase can leverage Storj as underlying storage provider.

Storj is capitalizing on the power of Blockchain to ensure global storage redundancy. Storj’s storage network consists of thousands and thousands of (user-run) nodes across more than 80 countries.

A Node’s reputation, latency, and a random weight decide if a Node is assigned to store your files. This way Storj makes sure your files will be accessible even if you unplug your local NAS connected to Storj.

Storj makes sure there are at least 3 to 4 copies of the file stored across multiple nodes in the network in the same “Satellite”, which is a region like Americas, Asia Pacific or Europe.


Century Link Object Storage


Centurylink, now rebranded/acquired by Lumen is one of the world’s largest internet backbone providers.

Lumen has a storage solution. And it’s fast.

Their cloud platform is relatively new, but given their strong networking background, this sure is a competitor!

Lumen’s solution is “based on a popular software package”, which we guess is Openstack’s Swift.

You’ll have to work your way through literally awful documentation, which is messy and primed for dotNet developers, if you can even find API documentation. Chances are you’re going to be on the phone with their support engineers and/or your account manager in order to get something done.

But hey, having a backbone attached to your storage solution, AND having an awesome API along with it, just looks too good to pass up on.