I'm worried about DigitalOcean. I think their priority should be to try to approach feature parity with Amazon or Rackspace. As of now, there are many features that are missing, such as private networking (only available in NYC2), CDN, elastic IP, load balancing, etc.
How about the ability to support attaching metadata to any instance?[0] How difficult is this to implement? More importantly, how would a devops person manage many instances without this feature? Isn't ex-EC2/Rackspace/<others> the target market for DigitalOcean?
Not to mention IPv6. I like DigitalOcean but am starting to think of completely ditching them not just because they don't have it (delays are understandable), but because the last word from them (around August or September last year) was that they'd have a public beta in October, and then gone completely silent.
No public beta happened, and now they won't respond to any customer queries about it. I'm fine with there being delays, but very not fine about the silent treatment (or vague answers like 'it's in development' - actually give some detail of what's been going on because it's been 'in development' for something like three years now).
You hit the nail on the head. We provided, and more specifically, I, directly did, estimates on when we launch certain features.
Unfortunately those deadlines have come and gone. That was because those estimates were rooted in timeframes around how we were able to write code in 2012 when we didn't hit the large growth spurt we did in 2013.
As a result the majority of 2013 was about meeting customer demand. Luckily we've finished out the year very well in scaling the various teams within the company and adding in the necessary layers of management so that we finally feel that we are getting back on track with engineering again.
With the launch of Singapore there are actually alot of updates under the hood that customers don't see but the hypverisors in Singapore are running on a completely new version of our cloud backend.
As we close out February we are reviewing our product roadmap and will start providing feedback again on estimates and hopefully be once again much more accurate in those estimates.
One of the other items we've considered is putting together a blog post about our 2013 in review and specifically focusing on what happened to our product roadmap and what delays we hit and why, and how we are looking to get past those challenges in 2014.
Comments
I'm worried about DigitalOcean. I think their priority should be to try to approach feature parity with Amazon or Rackspace. As of now, there are many features that are missing, such as private networking (only available in NYC2), CDN, elastic IP, load balancing, etc.
How about the ability to support attaching metadata to any instance?[0] How difficult is this to implement? More importantly, how would a devops person manage many instances without this feature? Isn't ex-EC2/Rackspace/<others> the target market for DigitalOcean?
--- [0]: http://digitalocean.uservoice.com/forums/136585-digitalocean...
Not to mention IPv6. I like DigitalOcean but am starting to think of completely ditching them not just because they don't have it (delays are understandable), but because the last word from them (around August or September last year) was that they'd have a public beta in October, and then gone completely silent.
No public beta happened, and now they won't respond to any customer queries about it. I'm fine with there being delays, but very not fine about the silent treatment (or vague answers like 'it's in development' - actually give some detail of what's been going on because it's been 'in development' for something like three years now).
I guess the reason is because their focus is primarily on expansion. They're trying to put on their big boy pants too soon.
Or they're simply under investor pressure to put on those big boy pants over achieving feature parity.
Or they're simply, you know, responding to demand.
You hit the nail on the head. We provided, and more specifically, I, directly did, estimates on when we launch certain features.
Unfortunately those deadlines have come and gone. That was because those estimates were rooted in timeframes around how we were able to write code in 2012 when we didn't hit the large growth spurt we did in 2013.
As a result the majority of 2013 was about meeting customer demand. Luckily we've finished out the year very well in scaling the various teams within the company and adding in the necessary layers of management so that we finally feel that we are getting back on track with engineering again.
With the launch of Singapore there are actually alot of updates under the hood that customers don't see but the hypverisors in Singapore are running on a completely new version of our cloud backend.
As we close out February we are reviewing our product roadmap and will start providing feedback again on estimates and hopefully be once again much more accurate in those estimates.
One of the other items we've considered is putting together a blog post about our 2013 in review and specifically focusing on what happened to our product roadmap and what delays we hit and why, and how we are looking to get past those challenges in 2014.
Thanks!