3 ms·
No, 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 Elastic
by bdcravens 8y ago
No, 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.
- scarface74 8y agoThere is a distinction but it has little to do with Linux. Netops - do you know how to properly configure AWS resources and architect it. This has nothing to do with Linux. If you want to tie your fate to AWS (no judgement), you learn how to do that via the AWS Console, the CLI, CloudFormation or scripting. If you don't want to tie yourself to AWS, use something like Terraform. Devops: If you're a Windows shop, you can set up a Windows Jenkins server (I wouldn't) or use a CodeBuild agent running on Windows EC2 instance. If you're using Lambda, you can use one of prebuilt Docker containers and create a yml file to run your commands. You can then either use a Lambda or CloudFormation template for deploying your code (if it's a Lambda function - never tried using CF for any other type of deployment) If you're a Windows developer using the various AWS services, you use the appropriate package. Where does having to know Linux come in if you're not developing on Linux?
- bdcravens 8y ago> Where does having to know Linux come in if you're not developing on Linux? If the job you're applying for indicates they're not using Linux, then it has nothing to do with it. If a company indicates the generic "cloud", in lieu of further constraining criteria, it's reasonable for them to assume the bulk use case (EC2 was the 2nd service launched on AWS, and there are millions of EC2 instances running; it's hardly a dying platform)
- scarface74 8y agoCheck out the top links on Indeed for AWS. How many of them have Linux as a requirement as opposed to knowing the different AWS technologies? I never said that EC2 instances were obsolete, but as a "cloud architect", companies aren't bringing you in for what you can do within an EC2 instance besides probably bootstrapping it using start up scripts. That's what the developers are for. There are plenty of all Windows shops using AWS as far as development. Even if you came in as an "Cloud consultant" to a shop that was doing everything on prem running Linux, they have Linux expertise in house, what they don't have is cloud expertise. Even if you have never touched a Linux computer in your life, you could still tell them how to develop using AWS technologies. All of the supported language SDKs work the same regardless of platfitndc.