171–180 of 194 posts
Has anyone used Vultr.com? I ask because they have all the same features as DO + way more (e.g. dedicated hosting w/ same great panel, BYO ISO, etc).
I have, I found their Sydney instances to lag for seconds at a time, completely randomly, while SSH'd in (I also live in Sydney, so it's not distance). I now have an instance with Digital Ocean in Singapore and I much prefer it.
Has anyone used Vultr.com? I ask because they have all the same features as DO + way more (e.g. dedicated hosting w/ same great panel, BYO ISO, etc).
Earlier quoted context omitted.
I'm not saying you're wrong but I disagree from my own POV. It's a common play in the hosting business to grow big quickly then sell out to a more enterprisey company (as happened with EV1Servers, Softlayer, Heroku) and if DO is taking such large amounts of funding, something will have to happen (IPO, acquisition, etc) and some companies don't make the transition well (I'm not saying DO wouldn't, but you never know).…
>> It's a common play in the hosting business to grow big quickly then sell out to a more enterprisey company (as happened with EV1Servers, Softlayer, Heroku) And that's exactly what Slicehost did, years ago. I wonder if Rackspace ever courted Linode. Slicehost always seemed to be the inferior one in price and performance.
Earlier quoted context omitted.
I'm not saying you're wrong but I disagree from my own POV. It's a common play in the hosting business to grow big quickly then sell out to a more enterprisey company (as happened with EV1Servers, Softlayer, Heroku) and if DO is taking such large amounts of funding, something will have to happen (IPO, acquisition, etc) and some companies don't make the transition well (I'm not saying DO wouldn't, but you never know).…
>> It's a common play in the hosting business to grow big quickly then sell out to a more enterprisey company (as happened with EV1Servers, Softlayer, Heroku) And that's exactly what Slicehost did, years ago. I wonder if Rackspace ever courted Linode. Slicehost always seemed to be the inferior one in price and performance.
Earlier quoted context omitted.
I disagree, Linode is much superior than DO. I can trust to DO only fault-tolerant services when to Linode I can trust any kind of service to run.
Clearly you haven't tried using their Fremont data centre. It's been terrible for years. And it's not like you have a lot of choices when it comes to Linode data centre. I'm sure your experience has been good, but there's a huge swathe of ex-Linode customers with pretty negative memories.
Earlier quoted context omitted.
Not sure why this is being downvoted but the whole Linode hack incident was a huge factor for me to switch all my VPS's over to digital ocean.
I went to Vultr. DO's interface is just as bad if not worse than Linode's. :(
I've recently switched from DO to Scaleway and would never go back.
Earlier quoted context omitted.
Serious question - What part of their UX do you think is game changer? I use DO and Linode. They both look similar to me. DO does have better UX than AWS, but I think DO is comparable to Linode rather than AWS. On the other hand, I think DO's content guides as a marketing tool is a great asset for them. I haven't seen any other provider do that. Linode had a few guides, but nothing as DO's scale.
You said it yourself when you mentioned the marketing and the community and the customer guides. User Experience is not just web interfaces, it's the whole user experience (man....) and that includes onboarding, self-service, support, learning and all the other small touches that make it a satisfying experience to be a DO customer.
1. No noise on the dashboard and intuitive process flow.
2. Very good forum and documentation. Site:digitalocean.com whatever-your-problem-is and you'll most likely get it resolved.
3. Little features like auto-populating the Gmail MX record values.
Earlier quoted context omitted.
Perhaps users don't have any complaints about their management interface? Do you? Perhaps users mostly want performance and value which have been greatly improved by their substantial infrastructure upgrades?
Yes. Their IP Failover is really badly documented and hard to work with. Their Nodebalancers are noticeably slow, the interface is alright, but you are better off setting up your own loadbalancer. I feel that static networking could be made easier, and more automatic when I am adding a new node. Their stackscripts should be able to receive parameters for when it is running, and the error-reporting should be better. I…
Earlier quoted context omitted.
> Name a business that has not had a 30 second outage in the past year? It's not a 30 second outage! Your domain will keep resolving the bad IP. Even with an extremely low TTL (also not recomendable) ISP's DNS will cache it and even some will ignore your TTL. A big portion of all new users will keep hitting the bad IP. Anyway, I won't try to convince you to change your setup if you are happy with it, but it's obvious…
> It's not a 30 second outage! Your domain will keep resolving the bad IP. Even with an extremely low TTL (also not recomendable) ISP's DNS will cache it and even some will ignore your TTL. A big portion of all new users will keep hitting the bad IP. So with 5 load balancers, 1/5 of customers see a one time hit of 30 seconds (after which they return to full speed). What better solution for the same price do you propo…
Nothing, your solution is obviously better than having none and it's enough for your needs. But the original discussion was about what's needed for DO to become a competitor for big business, not low budget, there they are already king.
Normally you want at least IP failover, meaning that you get an IP and can be rerouted to a different server with an simple API call. At work we use hetzner, which is not exactly a high-end provider but offers it: http://wiki.hetzner.de/index.php/Failover/en
Then, can be even better if the provider offers this HA-load balancer as a service, so you don't have to setup anything.
You might still need DNS failover to recover from a full datacenter going offline.
Earlier quoted context omitted.
I went to Vultr. DO's interface is just as bad if not worse than Linode's. :(
Why Vlutr and not something like Scaleway ( https://www.scaleway.com/ )? I've recently switched from DO to Scaleway and would never go back.
It was literally 10x slower than Linode even after playing around with Go's concurrency level to find the fastest runtime, and even with the dataset in memory. :( ARM just wasn't the right arch for what I was doing.
I ended up going with Vultr because it has the $5 pricepoint for hosting tiny websites and tons of datacenter locations. Their CPU performance and network speed were great in my tests.
[1] https://github.com/robinsonstrategy/go_backtesting_simulator...