Live data from Hacker News

DigitalOcean launches its container service

techcrunch.com

221–230 of 256 posts

Re: DigitalOcean launches its container service

#221
I am kinda confused... On the one hand, most people here seem to be fans of the DO services and praise their simplicity, on the other hand, I see their page an wonder what they are offering...

The names of their services seem to be equally confusing as the AWS names. Yes, overall their portfolio is closer to the actual use-cases (as in 'I want to have a blog' -> they have an offer for that), but I am still wondering what a droplet is (looks somehow similar to a Virtual Private Server).

When Hetzner released their cloud service earlier this year, I tried it, loved it and still do. Sure they don't offer the same products (e.g. no S3/Spaces), but at least they use established technical terms instead of some made up marketing names you have to learn for again for every new cloud hoster you want to try.

Re: DigitalOcean launches its container service

#222

Earlier quoted context omitted.

I am a mechanical engineer who dabbles in web development from time to time. I am forever indebted to DigitalOcean for creating a super easy platform for someone who has no clue about VPS starting out. I know how to operate a linux machine but not the slightest idea about how to host a website myself until I came across DigitalOcean and their LAMP/LEMP tutorials. Once I was comfortable with DigitalOcean, I tried laun…

Hi! I'm a member of the Community team at DigitalOcean. I wanted to thank you for your kind words about our tutorials. This kind of feedback means a lot to us. We're glad we could help you get your web site set up.

I'm a customer, but half the time I'm using your tutorials it's for home projects not my VPS.

Really great job!

Re: DigitalOcean launches its container service

#223
post #74

Earlier quoted context omitted.

I agree. I like that Digital Ocean takes their time to get a new product offering right. It shows. Especially when you compare it to AWS, which we're in the process of moving away from.

Just wondering which provider did you choose to go with instead of AWS?

Digital Ocean. We compared AWS, Google Cloud Platform, and Digital Ocean. While the latter isn't an apples-to-oranges comparison like the other two are, we found that the price, ease of use, and reliability made it the best choice.

I'm not yet sure about support since they don't offer any phone support. But it can't be worse than Amazons where I once literally had to yell at the support rep to stop talking because he just kept repeating himself, over and over, and wouldn't let me move on.

Re: DigitalOcean launches its container service

#225

Earlier quoted context omitted.

AWS used to be easy, but over the last decade it's become a specialization. Every time I wander back to it, there's another layer of complexity in the way towards doing something simple.

I agree. It seems like a deliberate strategy. Amazon is trying to create a breed of highly paid AWS experts who will be keenly interested in promoting AWS, because their valued knowledge is provider-specific and not transferable. Similar to how Microsoft created all those MCPs who tried to push Microsoft tech everywhere regardless of how well it fit the task.

It's mostly just the natural evolution of catering to their #1 entity - large corps.

I don't think they care about the long tail.

The 'specialization' may just be an advantage, maybe not.

Re: DigitalOcean launches its container service

#227
post #212

Earlier quoted context omitted.

Hey Rolleiflex - Thanks so much for being a DigitalOcean customer! We would be happy to increase your Droplet limit if you get in touch. Just visit the support link from your Cloud control panel to make the request or drop me a line directly (first name @). Thanks! Zach Director of Support, DigitalOcean

May be they should allow customer to set higher default limit instead of 10? Which is silly. ( I never knew there was such a low limit of 10 instances. )

I thought the limit was for your protection and you can get it increased just by contacting them?

Re: DigitalOcean launches its container service

#228
post #167

Earlier quoted context omitted.

DO's prices are why I'm a fan.

We are heavy users of GCP and AWS, but still use DO for bandwidth-heavy workloads.

AWS bandwidth charges are brutal, they are the secret billing item that kills products.

It can't make sense to host any kind of web anything when paying 10 cents / Gig egress charges.

If you have images at all ... nogo.

It's really odd, like they don't want your business because that's definitely one line item that always makes me keep my eye on the exit.

Re: DigitalOcean launches its container service

#229
post #14

So now that's managed K8S, managed databases, load balancers, a cloud firewall that's partially VPC like, object storage and block storage. Curious what's next. Lambdas maybe?

We have a big roadmap for 2019. Queues are interesting and so are functions in general. Nothing to share today but those are items we are assessing for future roadmaps :)

Any chance you can bump me up in the queue for getting managed DB beta access?

Re: DigitalOcean launches its container service

#230
post #95
post #51

Earlier quoted context omitted.

Is there a good way to sandbox terraform configurations? I'm not directly involved (just hear the screaming) but everything I'm hearing is that making modifications is a test of willpower. For us it's been about as transparent as a brick wall and I'm not clear if that's down to our bureaucracy or built into the design. Both are anathema to the goal of making complex deployments straightforward and self-describing (yo…

The recommended way, at least for AWS, is to have multiple accounts. One for production, and then however many more for test and development. Separate accounts let you run TF changes and know you will not impact production. TF can be tricky to grok at first especially if you don't have everything in TF. But, I couldn't imagine managing more than a server or 2 without it or something similar at this point. Once you ge…

Declarative syntax is notoriously hard to debug, especially for newbies.

As a general rule, if you're giving someone a tool that uses declarative syntax, you also need to provide them a private (not shared) sandbox in which to test out theories, try new things, and reproduce errors seen in production.

Since we don't have that, TF is pretty much the worst solution for our problems. Kube or even Docker Swarm would serve us much better.

Post reply on HN