4 ms·

I have settled on the ECS camp as well. Took a run at Kubernetes and was blown away by the complexity. With ECS/Fargate I don't spend any time on it. It just wo

by mr337 4y ago

I have settled on the ECS camp as well. Took a run at Kubernetes and was blown away by the complexity. With ECS/Fargate I don't spend any time on it. It just works for our setup. I still wonder from time to time if I am missing something not going Kubernetes.

adra 4y ago
Are you big enough to need terraform? If the answer is yes, you may have a good justification to move to kubernetes migrate tf->k8s with lots of benefits for the app teams (if they care). If you're just yolo setup your cloud in AWS web console and you're fine with that, then you may not see much lift. A good reason to use declarative (often infrastructure as code) approach to deployments is that it improves bus factor and the ability to hire people who can pick up and maintain the infrastructure.
- bernf 4y ago
  AWS CDK exists and IMO is way better than terraform if you're on AWS. So much so that terraform is making their own variant to be more CDK like.
  - mr337 4y ago
    I didn't know they were trying to be like CDK. Now I have to look this up :)
    - glenngillen 4y ago
      The CDK for Terraform went GA today (https://www.terraform.io/cdktf https://www.terraform.io/cdktf and https://www.hashicorp.com/blog/cdk-for-terraform-now-generally-available https://www.hashicorp.com/blog/cdk-for-terraform-now-general...). It's a framework that extends the capabilities of CDK so that you can use the whole Terraform ecosystem of providers and modules. Under the hood it means that the `cdktf synth` command ultimately generates Terraform configuration that can be executed like any other Terraform config. It's definitely not a case of Terraform trying to be like CDK. Each has it's strengths, choose whichever makes the most sense for your workflow.
- mr337 4y ago
  We are big users of terraform. I couldn't imaging running our setup without it or some other tooling like CDK.
- nazka 4y ago
  What about Pulumi? I love it

by mr337 4y ago

adra 4y ago

Are you big enough to need terraform? If the answer is yes, you may have a good justification to move to kubernetes migrate tf->k8s with lots of benefits for the app teams (if they care). If you're just yolo setup your cloud in AWS web console and you're fine with that, then you may not see much lift. A good reason to use declarative (often infrastructure as code) approach to deployments is that it improves bus factor and the ability to hire people who can pick up and maintain the infrastructure.

bernf 4y ago
AWS CDK exists and IMO is way better than terraform if you're on AWS. So much so that terraform is making their own variant to be more CDK like.
- mr337 4y ago
  I didn't know they were trying to be like CDK. Now I have to look this up :)
  - glenngillen 4y ago
    The CDK for Terraform went GA today (https://www.terraform.io/cdktf https://www.terraform.io/cdktf and https://www.hashicorp.com/blog/cdk-for-terraform-now-generally-available https://www.hashicorp.com/blog/cdk-for-terraform-now-general...). It's a framework that extends the capabilities of CDK so that you can use the whole Terraform ecosystem of providers and modules. Under the hood it means that the `cdktf synth` command ultimately generates Terraform configuration that can be executed like any other Terraform config. It's definitely not a case of Terraform trying to be like CDK. Each has it's strengths, choose whichever makes the most sense for your workflow.
mr337 4y ago
We are big users of terraform. I couldn't imaging running our setup without it or some other tooling like CDK.
nazka 4y ago
What about Pulumi? I love it