Do I understand correctly that they provide the manager nodes for free?
Yes, this is the pricing model for everyone except EKS/AWS as I understand it. Manager nodes are bundled with whatever you spend on your worker nodes. Google has gone so far with GKE as to offer HA masters distributed across availability zones at no extra cost. (On the day that Amazon announced EKS general availability, if I remember correctly, which is priced at $250/mo base cost, before you even get around to spend…
DigitalOcean launches its container service
71–80 of 256 posts
Re: DigitalOcean launches its container service
#72Serious 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.
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, blissfully unaware of which hosting provider it lives on.
This model allows us to be portable and avoid vendor-lock in, and a cross-provider infrastructure lets us gracefully handle system failures while keeping costs down.
Re: DigitalOcean launches its container service
#73Been a user of DOs beta kubernetes service and it works well. Though I would say the title of the linked article is a bit misleading. It is a Kubernetes as a service, like EKS, GKE and AKS. But not vanilla container service a la ECS, Fargate, the former Docker Cloud, etc.
Re: DigitalOcean launches its container service
#74I'm happy to see DO get some attention. I hope this means that really good hosting services like DO can still thrive in the age of AWS. DO seems to be doing well.
Re: DigitalOcean launches its container service
#75Re: DigitalOcean launches its container service
#76Earlier quoted context omitted.
Yes, this is the pricing model for everyone except EKS/AWS as I understand it. Manager nodes are bundled with whatever you spend on your worker nodes. Google has gone so far with GKE as to offer HA masters distributed across availability zones at no extra cost. (On the day that Amazon announced EKS general availability, if I remember correctly, which is priced at $250/mo base cost, before you even get around to spend…
I think it's more like $100/month base, but still infinitely more expensive than any other provider :(
This is a huge number compared to the competition, but also a rounding error when it comes to the monthly infrastructure spend expenses of Amazon's target market here.
I mean, to be fair, that's a really reasonable price for a HA cluster. If you ignore the pricing models of literally all of the competitors' offerings.
Re: DigitalOcean launches its container service
#77Earlier quoted context omitted.
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 :)
Is application hosting (heroku, app engine, elb) on the roadmap?
Re: DigitalOcean launches its container service
#78Re: DigitalOcean launches its container service
#79DigitalOcean has always been behind the curve of these things. All of the other big cloud platforms have had this for at least a few months. I haven't actually seen anything 'new' come out of DigitalOcean in years.
Were they ever 'new' in anything? I use them for small personal projects (they've gotten a lot more stable recently). I never thought of them as an innovative cloud provider but just one that was cheap and easy.
Re: DigitalOcean launches its container service
#80Earlier quoted context omitted.
what makes ECS 'vanilla'? i thought it was just a bespoke competitor to K8s.
Maybe you're thinking of EKS? ECS is an extremely basic scheduler that's closer to Nomad.
ECS on the other hand, is a so-called "vanilla" container service which provides its own abstractions and offers no suite for conformance, or compatibility with other vendors' offerings. I have not heard lots of people say great things about ECS. If I could say one nice thing, it's that there is probably less to learn about ECS than about Kubernetes.
[1]: https://www.cncf.io/certification/software-conformance/
[2]: https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4Eb...