Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean launches its container service

techcrunch.com

Post reply on HN
Print view View original

161–170 of 256 posts

Re: DigitalOcean launches its container service

#161

Post by sonnyblarney »

fermienrico wrote: post #105
talkingtab wrote: post #86

DO's kubernetes release is an an example of why I am a big fan. As a sole developer, I can't afford high technical debt, but DO packages tech in a way I can manage. I hope they keep on and wish other services (here's looking at you AWS) would package their services as well.

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…

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.

Re: DigitalOcean launches its container service

#163

Post by dylanz »

thinkshiv wrote: post #20
tyingq wrote: 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 :)

Ping me about queues!

Re: DigitalOcean launches its container service

#164

Post by homero »

talkingtab wrote: post #86

DO's kubernetes release is an an example of why I am a big fan. As a sole developer, I can't afford high technical debt, but DO packages tech in a way I can manage. I hope they keep on and wish other services (here's looking at you AWS) would package their services as well.

Aws has as light sail

Re: DigitalOcean launches its container service

#165

Post by skissane »

rolleiflex wrote: post #155
bphogan wrote: post #125

Earlier quoted context omitted.

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.

Thanks for the tutorials and for keeping them up to date. I’m probably not their target audience for the most part, but when I need to do something in an unfamiliar stack, [stack name] + digitalocean is usually my first search. Wish you guys had a little more of a professional oriented products (think AWS/GCP) and no ‘max 10 servers’ kind of rules so I could use it.

> no ‘max 10 servers’ kind of rules

You can contact their Support to get that increased. Just guessing at the reason, but if there was no limit, what happens if someone hacks your account and spins up a 100,000 node cryptocurrency mining farm?

Re: DigitalOcean launches its container service

#166

Post by rolleiflex »

skissane wrote: post #165
rolleiflex wrote: post #155

Earlier quoted context omitted.

Thanks for the tutorials and for keeping them up to date. I’m probably not their target audience for the most part, but when I need to do something in an unfamiliar stack, [stack name] + digitalocean is usually my first search. Wish you guys had a little more of a professional oriented products (think AWS/GCP) and no ‘max 10 servers’ kind of rules so I could use it.

> no ‘max 10 servers’ kind of rules You can contact their Support to get that increased. Just guessing at the reason, but if there was no limit, what happens if someone hacks your account and spins up a 100,000 node cryptocurrency mining farm?

The same thing applies to AWS, and AWS doesn't have '10 servers maximum' limit.

Beyond anything, it tells people about their target audience, which is indie development. That's fine, and it's a great market to be in. But in the case I have to spin up 17 servers in 24 hours in three continents, I can't really afford to deal with DigitalOcean's support under that kind of stress. This doesn't happen often, but when it happens, it absolutely breaks you.

Re: DigitalOcean launches its container service

#167

Post by aviv »

sonnyblarney wrote: post #160
talkingtab wrote: post #86

DO's kubernetes release is an an example of why I am a big fan. As a sole developer, I can't afford high technical debt, but DO packages tech in a way I can manage. I hope they keep on and wish other services (here's looking at you AWS) would package their services as well.

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.

Re: DigitalOcean launches its container service

#168

Post by hosh »

jopsen wrote: post #93
tlrobinson wrote: post #73

Earlier quoted context omitted.

Maybe this is a dumb question, but couldn't/shouldn't a KaaS (and other orchestration systems) just be a layer on top of "vanilla" CaaS?

Don't you need to setup network paths? And connect containers to each other.. Then setup/teardown in specific order.. and if you have state, keep a subset of containers alive to avoid loosing state (even if it's replicated).

Kuberneted is designed in a way where stateless pods (collection of containers sharing the same ip and identity) are decoupled from stateful ones. There are concepts designed into K8S that allows components to attempt to self-heal.

For example, a pod that requires a postgresql pod to connect to will fail and crash out. The scheduler will start a new one. If the postgresql pod is up by that point, then the rescheduled pod will no longer crash.

As far as the network paths, one of the really cool things about pods running inside a k8s cluster is that they can access any of the other pods, even if they are on a different node. However, pods typically reference services (such as postgresql) by dns name. You specify the set of pods that belong to the service by label selector. This allows the pods to come up, tear down, crash, moved to another node, while the service maintains a stable point of contact. It is quite brilliant, and other orchestrators quickly tried to copy it.

Stateful workloads are still difficult. Each distributed stateful system has its own way of setup and teardown. What we will probably see are custom Operators designed for each distributed stateful system, coming out over the years.

Re: DigitalOcean launches its container service

#169

Post by wise_young_man »

mark-ruwt wrote: post #72
rfinney wrote: post #34

Serious question: Is there an emerging cross platform workflow language to just write stuff to run on any cloud/container hosting setup? The idea would be to be portable, avoid vendor lock-in and take advantage price differences or quickly route around a system failure in one of the providers.

We rely on bash. Each machine that's spun up is built from scratch via one command-line call. The first half of the process interacts with each hosting API (we rely on DigitalOcean, Linode, and Vultr primarily), to build a clean slate machine with all of the packages and libraries that we expect. The second half of the process runs the actual build process, building the instance step-by-step on top of the clean slate…

I made something similar and turned it into a service [1] focused on WordPress, but unfortunately there hasn't been much interest from people as I thought there would be, though that could be due to my lack of marketing.

My goal was the same, to make hosting more portable with features like snapshotting and restoration of WP sites across servers and to even eventually expand beyond just servers, to bring in domain registrars and cloud storage to be able to move things around easier. For example: you have a site hosted on AWS EC2 with DNS at Namecheap and nightly backups at Dropbox and let's say the AWS Virginia region goes down. You create a new server in Digital Ocean and restore the snapshot from Dropbox and the linked DNS at Namecheap is auto updated.

The more I thought about this though, I began to realize that maybe these features wouldn't be useful to the audience I wanted to target, which was people who wanted to grow from shared hosting and have something reliable and less noisy neighbors, but still more affordable than managed WP hosts and lastly more control (bring your cloud/server provider).

[1]: http://pagefog.com

Re: DigitalOcean launches its container service

#170

Post by amichal »

rolleiflex wrote: post #166
skissane wrote: post #165

Earlier quoted context omitted.

> no ‘max 10 servers’ kind of rules You can contact their Support to get that increased. Just guessing at the reason, but if there was no limit, what happens if someone hacks your account and spins up a 100,000 node cryptocurrency mining farm?

The same thing applies to AWS, and AWS doesn't have '10 servers maximum' limit. Beyond anything, it tells people about their target audience, which is indie development. That's fine, and it's a great market to be in. But in the case I have to spin up 17 servers in 24 hours in three continents, I can't really afford to deal with DigitalOcean's support under that kind of stress. This doesn't happen often, but when it h…

AWS also has a initial soft limit on EC2 instances. I dont remember what it is but its <100
Post reply on HN