121–130 of 196 posts
As the article is from Jun 2013 I should point out the following link (also linked at top of article): http://trends.netcraft.com/www.digitalocean.com We have been publicly tracking DO at that address on a monthly basis (I work for Netcraft).
Serious question: is it really worth it for a company like DO to support Windows? It seems like they maintain their edge by avoiding the kind of complexity that Windows would entail.
You can't do a Windows VM for $5 between the facts that you need more RAM, more HD, and a Windows license.
To people wondering if this is a temporary thing, or what Digital Ocean's competitive advantage is (since someone else can come along with the same price point): It's that the web interface, and process for starting a "droplet", is dead-simple and super-elegant, their support docs are comprehensive and easy to use, and they even do things like let you manage your own DNS records. And it all just works. Digital Ocean…
I think in a nutshell you're describing Clayton Christensen process of disruptive innovation (or more specifically low end disruption). AWS is catering more and more to its most demanding users. This exposes them at the lower end to developers who aren't as demanding but prefer something simpler that better fits their needs. The way this narrative ends is that DO eats up AWS from below
When they added cloudfront, RDS or elastic beanstalk they were offering "something less flexible but very simple" even while they were adding glacier or MFA through IAM which are for more "complex" customers.
Earlier quoted context omitted.
I felt the same way for a while, but eventually, while working on a large cloud-based project, I had an epiphany: the GUI is basically the phpMyAdmin interface of AWS. phpMyAdmin is great when you're first learning to work with the LAMP stack; it lets you fiddle with values, manually create databases, munge columns, etc. But. If there are multiple instances of your system running "in the wild" (even just within your…
I would suspect AWS makes most of their money from clients that manage instances that are in the mid to high double digits and beyond. For these clients its likely that at some point automation has kicked in and the APIs get the job done much better versus having someone spend time clicking away in a browser.
But I think there are plenty of mid-sized comapnies with multiple AWS accounts, with many machines in each one where no one is quite sure what they do or if they can be switched off.
To people wondering if this is a temporary thing, or what Digital Ocean's competitive advantage is (since someone else can come along with the same price point): It's that the web interface, and process for starting a "droplet", is dead-simple and super-elegant, their support docs are comprehensive and easy to use, and they even do things like let you manage your own DNS records. And it all just works. Digital Ocean…
With D.O. there's an ambiguous list of things you need to do to upgrade to a new plan. For example, after shutting down to upgrade, I heard you need to backup your disk image to multiple datacenters because sometimes an image can get deleted by accident. One night I spent several hours trying to (safely) upgrade and support was slow to respond, eventually I gave up. With Linode it's just a few clicks and you can see the progress of the migration in the dashboard, it's very easy.
I use both Linode and D.O. but for personal projects, Linode is my choice because their tech support team is very responsive 24/7. I am not a heavy user of tech support but when I do need help I need it fast!
Earlier quoted context omitted.
I think in a nutshell you're describing Clayton Christensen process of disruptive innovation (or more specifically low end disruption). AWS is catering more and more to its most demanding users. This exposes them at the lower end to developers who aren't as demanding but prefer something simpler that better fits their needs. The way this narrative ends is that DO eats up AWS from below
I think you mean "DO gobbles up the fruit that fell from the AWS tree". Why on earth would AWS be particularly concerned that DO gets all the people who want to spend $5/server and have a handful of servers, when AWS get all the people with four-figure-plus spends? One $1000 spender is worth 20 people who rave over $5 boxes. And there are plenty of $1k spenders. AWS does have some cheap offerings - some micro instanc…
Earlier quoted context omitted.
I've been using DO for a few months. I recently set up an AWS instance to use as a proxy, as I wanted something cheap in East Asia temporarily, and AWS's Tokyo region fit the bill. Holy crap is AWS bizarre to set up. I got it done without too much trouble in the end, but man, the UI is just atrocious. It took way too long just to find the right place to go to get started with the process.
I felt the same way for a while, but eventually, while working on a large cloud-based project, I had an epiphany: the GUI is basically the phpMyAdmin interface of AWS. phpMyAdmin is great when you're first learning to work with the LAMP stack; it lets you fiddle with values, manually create databases, munge columns, etc. But. If there are multiple instances of your system running "in the wild" (even just within your…
Seems no one here so far has mentioned Rackspace. Let's start by saying that DO has fewer features for a complex deployment: No load balancing, no private subnets, (IIRC) no IPv6 at the moment. No "cloud files" or S3 equivalent, the scaling isn't as automatic as RAX or AWS can provide. DO can't host Windows (which still matters for many existing operations, don't fool yourself). RAX gives more information and granula…
Earlier quoted context omitted.
I felt the same way for a while, but eventually, while working on a large cloud-based project, I had an epiphany: the GUI is basically the phpMyAdmin interface of AWS. phpMyAdmin is great when you're first learning to work with the LAMP stack; it lets you fiddle with values, manually create databases, munge columns, etc. But. If there are multiple instances of your system running "in the wild" (even just within your…
[deleted]
If you are writing a Python, PHP, Go, or Java web app, I think using Google App Engine is the easiest way to get your app live. DigitalOcean is easy, but it still requires you to know a bare minimum of Linux-Fu. App Engine is just brain-dead easy. You literally execute a deploy script locally. And as an added bonus, if you use the Google datastore instead of their RDBS it should scale smoothly too.