5 ms·
I would compare the lack of Linux fundamental skills and working in the Cloud arena, to learning cursive before learning to print. You might be able to pull it
by indigodaddy 8y ago
I would compare the lack of Linux fundamental skills and working in the Cloud arena, to learning cursive before learning to print. You might be able to pull it off, but the advantages to understanding the Linux building blocks behind the cloud magic cannot be understated. There will be numerous situations where having these skills in your back pocket can solve problems that aren't necessarily articulated in standard cloud workflows.
- scarface74 8y agoWhat would that be? In AWS everything is managed and the only time that you actually get near the OS are EC2 instances for some custom programs when you aren't using Docker/Fargate (serverless Docker) or Lambda and every now and then a few shell scripts. Any complicated sceneries usually revolve around scripting AWS resources and for that I would use Python.
- bdcravens 8y agoHow are you creating Docker containers of any complexity without understanding Linux?
- scarface74 8y agoI'm using Docker just as a serverless app container with Fargate for long running apps - services that are inappropriate for Lambda. All of the infrastructure resources are managed AWS services - configuration, databases, load balancers, messaging, autoscaling, etc. For Windows stuff, I'm using autoscaling EC2 instances. The issue like I said above is that the granularity for billing Windows EC2 instances is 1 hour compared to per second billing for Linux instances. I'm not anti-Linux but the ops stuff for AWS revolves around either scripting with the CLI and batch files for simple stuff or Python+Boto3 for the more complicated scenarios. As a developer, all the resources are managed, you never touch the underlying OS.
- bdcravens 8y ago> I'm using Docker just as a serverless app container with Fargate for long running apps - services that are inappropriate for Lambda. But what are you doing in that Docker container? Anything more than just pulling the default container? Every container I've built required pulling packages, setting some permissions, etc. A Docker container isn't OS-less, and you still have to be mindful of the same concerns as if it wasn't a container. > As a developer, all the resources are managed, you never touch the underlying OS. Sure. Though I'd posit is that if all you're doing is using fully managed services on AWS, it's akin to installing and configuring Wordpress - you use PHP, but you're not a PHP developer.
- scarface74 8y agoWhy would you use AWS and then create a bunch of EC2 instances to host servers for databases, caching, ElasticSearch, messaging, configuration, orchestration, etc? That kind of defeats the purpose of going with AWS. If all you're doing is using a bunch of EC2 instances to simulate what you're doing on prem, you might as well go for much cheaper VPS providers. AWS is not buying you anything if you're still managing all of your own servers.
- bdcravens 8y agoWe're on ECS now (using EC2 - for persistent workloads, Fargate is much more expensive), but we ran a lot of traditional EC2 containers for years. We ran alot of application code on EC2 while using services like SQS, RDS, etc. At one point we used Cloud66 that used our AWS backend. We do a ton of background processing; combined with spot instances, it's a great platform for scaling up and down in the hundreds of instances. In every one of these situations, there were often needs to SSH into those machines, review log files, look at htop, etc. Even for the "VPS use case" AWS provides compelling advantages: better firewall control, image management, VPC isolation, API automation, etc.
- scarface74 8y agoThe post I was replying to said. > As a developer, all the resources are managed, you never touch the underlying OS. Sure. Though I'd posit is that if all you're doing is using fully managed services on AWS, it's akin to installing and configuring Wordpress - you use PHP, but you're not a PHP developer That seems to come with the implication that if you're using managed services like SQS (instead of installing your own message service), RDS (instead of installing your own database), and you're using other AWS services you're not a "real developer". If you're using some of the surrounding services, it makes perfect sense to use AWS.