Fork me on GitHub
#architecture
<
2017-04-11
>
yonatanel10:04:30

Is Pallet dead? How do you usually provision on the cloud? Cloudformation, Terraform etc?

dominicm12:04:19

We use terraform/packer.

yonatanel13:04:03

@dominicm Can you say why terraform and not something else?

dominicm13:04:54

Because it's declarative. Which means that the file represents your target infrastructure. Not a history of changes susceptible to breaking if someone alters aws

dominicm13:04:10

The JSON format is good for generating to

yonatanel14:04:05

Isn't cloudformation declerative as well? Maybe I don't know enough about them yet.

dominicm15:04:46

I hear cloudformation is really crap.

lmergen16:04:59

I concur, we have everything in cloud formation, and I would never choose that again

lmergen16:04:19

it's inconsistent, feedback cycles are really long, and we've had three occasions where cloudformation failed while rolling back, causing the entire stack to be in a corrupted state

lmergen16:04:50

on top of that, you're basically locking yourself into AWS

lmergen16:04:45

also, they managed to invent some pseudo-programming language on top of JSON

fellshard16:04:54

It wants to be declarative

fellshard16:04:00

But without all the bits that make declarative useful

fellshard16:04:27

Kubernetes seems to be a more expressive take on that kind of concept - allocation, clustering, and scaling, etc.

lmergen17:04:10

I wouldn't compare it to Kubernetes

lmergen17:04:38

ECS is AWS' version of Kubernetes

fellshard17:04:32

It's not directly comparable, no. But when considering how to declaratively allocate resources, Kubernetes' type of model - objects that ensure specific constraints hold - might be superior to simply giving a specific state and not bothering with how transitions occur.