Introducing Object Storage
digitalocean.com
Introducing Object Storage
1–10 of 43 posts
Re: Introducing Object Storage
#2If there's anything I've learned about object storage over the last year, it is: don't use object storage unless you need it for a particularly narrow use case of silly data volumes or CDN storage for a massively distributed content network. Anything else, forget it.
It rarely if ever works properly with standard Linux or Windows tools (s3), it has a rat's nest of arbitrary restrictions which require a language lawyer to decypher (s3/iam/vpc/roles), the APIs are vendor specific and sometimes even region specific (s3), the APIs are obtuse (s3 multipart), the clients are buggy (boto/boto3), suddenly you inherit extra costs and configuration requirements if you want to do something like expose it over http (route53/cloudfront/s3), credential storage is a nightmare for distribution compared to rsync/ssh etc. Ugh.
Please note I have used Google Storage as well and all of the above also apply.
The only thing that is positive is capital expenditure is low.
Re: Introducing Object Storage
#3Slowly, very slowly, DO is creeping towards having enough features to peel users off of AWS and GCP. Block storage, load balancers, and now blob storage...if you don't need managed queues or databases, you can probably save some serious coin by running services on DO.
S3 sets a high bar in terms of durability and availability, so it will be interesting to see how well DO can compete, and it will take a long time to gain the same level of trust that S3 has earned.
Re: Introducing Object Storage
#4If there's anything I've learned about object storage over the last year, it is: don't use object storage unless you need it for a particularly narrow use case of silly data volumes or CDN storage for a massively distributed content network. Anything else, forget it. It rarely if ever works properly with standard Linux or Windows tools (s3), it has a rat's nest of arbitrary restrictions which require a language lawye…
Is there a stand for object storage?
Re: Introducing Object Storage
#5There's pretty much zero information on that page, so why should I care?
Re: Introducing Object Storage
#6If there's anything I've learned about object storage over the last year, it is: don't use object storage unless you need it for a particularly narrow use case of silly data volumes or CDN storage for a massively distributed content network. Anything else, forget it. It rarely if ever works properly with standard Linux or Windows tools (s3), it has a rat's nest of arbitrary restrictions which require a language lawye…
Is there a stand for object storage?
openstack swift supposedly but this is a slightly incompatible S3 implementation that nothing else talks.
The filesystem works pretty well though ;)
Re: Introducing Object Storage
#7Anybody have or see pricing after early access period?
Re: Introducing Object Storage
#8There's pretty much zero information on that page, so why should I care?
We roll out a public beta test with existing customers to ensure performance and reliability before doing a GA release. This allows customers to use the new product and provide feedback as well as help us to ensure a great level of service when the product goes full GA. So it's really a way for customers to test out new products early, but the specific details are specifically light so that if there are any major changes in the beta period we can roll them out.
Re: Introducing Object Storage
#9Anybody have or see pricing after early access period?
We aren't providing pricing information till full GA which is later in the year. All beta users will be given 1TB of free object storage during the beta period.
Re: Introducing Object Storage
#10If there's anything I've learned about object storage over the last year, it is: don't use object storage unless you need it for a particularly narrow use case of silly data volumes or CDN storage for a massively distributed content network. Anything else, forget it. It rarely if ever works properly with standard Linux or Windows tools (s3), it has a rat's nest of arbitrary restrictions which require a language lawye…
I think AWS CLI is pretty handy for lot of tasks. Not sure if you are referring to which multipart API of s3[1]. There is a higher level API for quite some time now which is very convenient. Agree about documentation for iam/vpc/roles being arcane but tbh I have no idea how that could be simplified.
[1] http://docs.aws.amazon.com/AmazonS3/latest/dev/usingHLmpuJav...
Edit: Added link to high level API