11–20 of 194 posts
I'm so excited for this. I'd previously commented about how the lack of non-SSD storage meant I had to screw around with S3 when I really just wanted to keep everything on DO.
Great company. Been with them for two years now, and couldn't be happier. Combined with Cloud66 I worry less about deployments and servers and backups, and more about just getting the code out.
> The $83 million is going directly into growing our team and expanding our product offerings with networking and storage features. Great to hear. Real private networking, object/shared storage and most importantly HA (IP failover/load balancing) is all DO is missing to start really competing with AWS for "big business".
Real private networking and object shared storage are both huge for sure though.
DOs announment talks about a storage product, which is strategically important and crucially something Linode has sorely needed for a long time. And yet the biggest development in recent years at Linode has been a proprietary stats and monitoring system built as an upsell, which doesn't really do anything distinctive that Nagios or another package couldn't provide.
Instead Linode is now switching their entire platform from Xen to KVM, a curious move which will create risk and cost velocity that could have been spent on product development.
I have been a huge supporter of Linode over the years, and the startup I co-founded is one of their biggest customers, but at this point DO seems like the winning horse to back.
> The $83 million is going directly into growing our team and expanding our product offerings with networking and storage features. Great to hear. Real private networking, object/shared storage and most importantly HA (IP failover/load balancing) is all DO is missing to start really competing with AWS for "big business".
I don't think HA is really on the needed list, seeing as you can roll your own load balancer in 5 minutes using provided tutorials. I mean I guess they could make an image for it to make it a little easier.. The AWS elastic load balancer is really nothing fancy. Real private networking and object shared storage are both huge for sure though.
If all goes well, looks like they might be competing directly with AWS soon.
DO is closer to competing with just Elastic Beanstalk and maybe RDS (from the standpoint of a managed RDBM service, not the feature set).
If all goes well, looks like they might be competing directly with AWS soon.
Obviously you can't fake some things with just VMs (rolling your own VPC for example is kind of hard to do), but a lot of people don't need Redshift or SQS or any of the amazon SAAS things...
If all goes well, looks like they might be competing directly with AWS soon.
Earlier quoted context omitted.
Honest question. How much would you pay to have something that manages the updates and setup for you and give you the sysadmin help when you need it?
That's what Rackspace does. I haven't used them in a while, but it looks like it's ALL they do now. (moved to DO, since it was half the cost and I /do/ have enough sysadmin chops to keep two linux servers patched). http://www.rackspace.com/cloud/compare-service-levels
Earlier quoted context omitted.
I don't think HA is really on the needed list, seeing as you can roll your own load balancer in 5 minutes using provided tutorials. I mean I guess they could make an image for it to make it a little easier.. The AWS elastic load balancer is really nothing fancy. Real private networking and object shared storage are both huge for sure though.
Have they implemented IP failover already? I haven't heard anything. Having your own LB without being able to fail over the IP is not HA. If the LB does down so does your business.
You use DNS failover and multiple load balancers.
FOO.COM A record -> 1.2.3.4, 1.2.3.5, 1.2.3.6
Then at 1.2.3.4, 1.2.3.5, and 1.2.3.6 you put a load balancer that splits loads between all of your clients.
Any LB goes down, and DNS client retries will deal with it. If any backend server goes down, your LB will deal with it.
Using this pretty successfully at digital ocean right now. What is the downside? I guess client DNS retries takes a few seconds, but for a rare case of a load balancer dying, seems not a deal breaker.