29 ms·
We run our infrastructure on both AWS and DigitalOcean. 1) DO consistently beats the price performance. 2) DO has simple pricing model --> No ondemand / reserv
by recmend 13y ago
We run our infrastructure on both AWS and DigitalOcean.
1) DO consistently beats the price performance.
2) DO has simple pricing model --> No ondemand / reserved instances
3) AWS is more feature rich but DO continues to add new functionalities like private networking and new data centers
- twistedpair 13y agoMust be nice to have your providers competing with each other. Everyone knows Bezos loves a good ole race to the bottom better than anyone. I suspect we'll see even steeper AWS price cuts this year in response.
- recmend 13y agoyup, competition drives innovation and is good for the cloud ecosystem.
- toomuchtodo 13y agoS3 price cut was nice. The EBS storage price cut was even more extreme (and fantastic) going from 10 cents/GB to 5 cents/GB. At Amazon's scale, you can make it up on volume.
- toomuchtodo 13y agoComparing DO to AWS is extremely disingenuous unless you're only comparing compute per $. Running in AWS, we get access to unlimited storage through S3, EBS volumes we can move between instances, a CDN, etc. Digital Ocean is like the place with a bunch of servers in the garage. Yes, its cheap. No, I would not trust it to run my business. I'm very interested to see how they think they can compete with AWS, considering Amazon's cost to acquire equipment and their AWS software engineering team.
- Patrick_Devine 13y agoYou're right about EBS, however I kind of scratch my head over S3. Yeah, I guess it's integrated in the sense that you can access it from the same account, however, try creating an EC2 instance without a publicly addressable IP. You can't access S3 at all from your VPC, which makes S3 not usable in many use cases.
- toomuchtodo 13y ago> however, try creating an EC2 instance without a publicly addressable IP. You can't access S3 at all from your VPC, which makes S3 not usable in many use cases. I don't see the problem with this. Either give your EC2 instance in your VPC a dedicated public IP and configure the security group to disallow all inbound connections, or use a public IP that routes all traffic for your VPC and again, secure it with a security group. We do this right now with our environment, as our application is heavily EC2<->S3 dependent. It works without issue.
- Patrick_Devine 13y agoMy use case is different. I want to put data into S3, but want it only accessible on my instances in the VPC, none of which I want to have access to the outside world. I realize many people probably don't have this particular need, however, I don't think it's completely unreasonable. Instead, I'm just mounting an EBS volume on an instance and running nginx to serve files.
- toomuchtodo 13y ago> My use case is different. I want to put data into S3, but want it only accessible on my instances in the VPC, none of which I want to have access to the outside world. Which you can still do, by using bucket policies/permissions in S3 (specifically EC2 IAM roles in this scenario). I think we're arguing different use cases though. If your content is only used or getting served from one machine, EBS volumes. If you need to have it served to the world, available to multiple instances, etc, S3.