3 ms·
How are you creating Docker containers of any complexity without understanding Linux?
by bdcravens 8y ago
How 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.
- bdcravens 8y agoNo, I think it's perfectly fine to leverage managed services. (We did however replace SQS with Sidekiq, as that was a better fit, and we do use Redis on Elasticache) I tend to take the position of letting AWS save me time and configuration, but being prepared to run those pieces outside of AWS (which I'm already doing when I develop locally) > That seems to come with the implication that if you're using managed services ... you're not a "real developer". Let's bring it back to the original point: "cloud" as a desired skill employers are hiring for. Obviously that's so ambiguous it's ridiculous, and maybe it should be split into "managed cloud services" and "infrastructure as a service". But as long as there are employers out there seeking "cloud" as a singular term, I think it's disingenuous to answer that call if you can only work with the managed pieces.