3 ms·
For someone with a good general understanding of systems (distributed systems, operating systems etc), but perhaps lacking in hands on experience of deploying i
by anonymousDan 5y ago
For someone with a good general understanding of systems (distributed systems, operating systems etc), but perhaps lacking in hands on experience of deploying in a specific cloud, what would you say the key things are to learn? For me they almost seem like trivial things you could pick up in no time on the job.
- Nextgrid 5y agoProduct-specific functionality & configuration. Every cloud provider has their own product, features & configuration for the same basic thing. In the past, if you needed a load-balancer & reverse proxy you'd use Nginx or HAProxy regardless of the underlying machine. Now in the cloud, although you can technically run it on a VM, it's not "best practice" and you should instead reimplement it using your cloud vendor's proprietary equivalent, whether it's AWS ELB/ALB or something else, and that experience isn't portable across competing clouds.
- criddell 5y agoI'm pretty confident that somebody who has been able to master one provider is going to be able to figure out a different one relatively quickly. I think that breadth of knowledge could ultimately be pretty valuable.
- pjerem 5y ago"In the past" ? My current employer, a high growth company uses HAProxy and Nginx in production with no plan to change anytime soon. Those are not tools from the past. They still work really well and there is no law requiring your brand new startup to be on AWS. Most companies (even more when they are B2B) have very predictable workloads.
- Nextgrid 5y ago> there is no law requiring your brand new startup to be on AWS See https://news.ycombinator.com/item?id=30272588 https://news.ycombinator.com/item?id=30272588.