S
Skyliner Blog
blog.skyliner.io · Company blog · on HN since 2016
The team behind Skyliner, an AWS deployment tool, wrote on deployment practices, Clojure and operations before joining MailChimp.
What HN saysA commenter calls the founder's essay on Google's Borg and Kubernetes awesome; HN otherwise links it for deployment and operations advice.
15HN people shared it
1linked it in comments
26stories submitted
749story points
4 years agolast shared
2016people per year2026
Most-shared posts
- 1Ship Small Diffs6 people · 180 points · first shared 2017 · 72 comments on HN
- 2You Can’t Have a Rollback Button3 people · 113 points · first shared 2017 · 57 comments on HN
- 3Risky Business Requires Active Operators3 people · 30 points · first shared 2017 · 2 comments on HN
- 4Fourteen Months with Clojure2 people · 307 points · first shared 2017 · 187 comments on HN
- 5The Happy Genius of My Household2 people · 4 points · first shared 2016 · discussion on HN
- 6A Simple Pattern for Jobs and Crons on AWS1 people · 48 points · first shared 2017 · 11 comments on HN
- 7Skyliner is shutting down and our team is joining MailChimp1 people · 32 points · first shared 2017 · 1 comments on HN
- 8Ship Small Diffs (2017)1 people · 15 points · first shared 2022 · 1 comments on HN
- 9Welcome to Skyliner: AWS is easy now1 people · 14 points · first shared 2016 · 2 comments on HN
- 10On the Difficulty of Conjuring Up a Dryad1 people · 2 points · first shared 2016 · discussion on HN
- 11No Way Out but Through1 people · 2 points · first shared 2016 · discussion on HN
- 12Virtual Machines Are Fleeting Things1 people · 2 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
xuejie · 2017-04-28
This reminds me of the awesome article by the founder of skyliner: https://blog.skyliner.io/the-happy-genius-of-my-household-2f76efba535a
Google built Borg/Kubernetes because they own all the host machines which are super powerful, and they need multiple apps on one machine to cut cost. But for the rest of us building apps, different VMs provided by cloud provider, such as EC2, already provides a nice way of resource isolation that is also cheap, so why do we need to run multiple containers per machine? Suppose c4.4xlarge is too big for your app, for cost effective reason, you want to leverage Kubernetes to run multiple apps on the same VM, why not just spawn multiple c4.xlarge or c4.2xlarge VMs, and run only one app per VM for you?
I admit this model won't fit us all, but for a significant number of us, this is already a good enough solution like containers, and it works today without needing to setup all kinds of fancy software defined networks, which we never know how long it's gonna last without signaling an issue.