Re:AWS services to avoid
by scarface74 on Sunday May 10, 2020 @07:46AM
(#23131912)
Terraform is not “cloud agnostic”. Every provisioner is specific to the platform.
Perhaps bad terminology on my part but I would argue that Terraform IS cloud agnostic, it is NOT cloud portable.
You can use Terraform with any cloud. You cannot seamlessly move your AWS configuration to Google Cloud but you can still write Google Cloud configuration with the same paradigm as your AWS configuration.
This is exactly the idea of Terraform - the workflow is portable and agnostic, but the full fidelity of each individual resource provider API is exposed.
which is fantastic. =)
At first I read: Every prisoner is specific to the platform. It seems to clarify the point anyways.
Right, but the HCL syntax and overall Terraform paradigm is not.
it’s not just the provisoner. it’s. it like different clouds have the same abstraction. for all intents and purposes you need to understand the underlying cloud and how to use api/tooling around it when terraform fucks up
The article contains at least one inaccuracy - no one has been using Terraform since 2012. The first commit was in May of 2014.
Terraform is "cloud agnostic" in the same way the Latin alphabet is "language agnostic."
Re:AWS services to avoid
by MrBuddyCasino on Sunday May 10, 2020 @09:10AM
(#23132322)
No reason to use Terraform when Pulumi exists.
I am about to start deploying with Terraform. Taking the big step.
Why should I use Pulumi over Terraform? (Genuinely wondering)
Re:AWS services to avoid
by MrBuddyCasino on Sunday May 10, 2020 @02:47PM
(#23134957)
People ask that question all the time, and I don't get why. I hate HCL, I hate the verboseness, the limited capacity for abstraction, that its yet another proprietary format, everything reminds me of ANT.
I want infrastructure as code, not infra-as-yaml. I want types checked by the compiler, as is good and proper. Apparently many people don't feel that way though?
To me, Pulumi is a godsend.
Elasticache is expensive and the analysis is generally correct on that, however if you do actually need a high capacity rock solid Redis cluster and you can afford it, it does the job. Paying someone to setup and scale a cluster of that magnitude would probably cost a year's worth of usage. Of course if you don't actually need to scale it yet then just use the suggestions in the article to run it yourself.