5 ms·
I prefer to use object storage powered by OpenStack Swift[1], which makes my application not attached to any proprietary API. [1] https://www.ovh.com/world/pu
by krn 8y ago
I prefer to use object storage powered by OpenStack Swift[1], which makes my application not attached to any proprietary API.
[1] https://www.ovh.com/world/public-cloud/storage/object-storage/ https://www.ovh.com/world/public-cloud/storage/object-storag...
- lostcolony 8y agoThere ya go then. Like I said; you're eschewing leveraging -any- managed service cloud providers give you, and instead just use bare VMs, and relying on cobbling together open source stuff, that you have to manage yourself, to build a solution. That's fine for those who have that kind of time, but some of us want to build things and push as many things onto the cloud provider as possible, so we don't have to deal with them. I like having out of the box authentication with Cognito, out of the box DBs with RDS and Dynamo, out of the box object storage with S3, Serverless as an option with the API Gateway and Lambda...and I'll worry about vendor lockin when Amazon ups the price of an AWS service.
- krn 8y agoYou are right, I prefer highly scalable and proven in production open-source tools, such as Redis and Postgres, to managed services by some cloud provider. It comes as very little overhead, if you pick the right tools and master them, then re-use. But I understand your point about just connecting a bunch of APIs and being done with it, if you personally don't own the product, or if you are expecting to sell it soon. A nitpick: I don't host my own object storage, I just pick S3 alternatives that provide standard APIs to access them.