Docker is a dangerous gamble which we will regret (2018)

Post by ta999999171 » Mon, Jan 27, 2020, 7:41 PM UTC

mywittyname wrote: post #61

k__ wrote: post #24

Earlier quoted context omitted.

The problem is, as so often, the system. If HR goes as low-level in hiring as "React Developer" then people have to play this game. If HR would hire on something more substantial, it wouldn't matter if you did Linode or AWS, React or Angular, Docker or Bash scripts.

Hiring people is difficult, exhausting, time-consuming, and largely a crap shoot, since hiring consists of deducing a person's technical abilities with around 1-2 hours of interaction in a very limited scope. If we could find a better way, we'd be using it. But, as it stands, recruiters and HR have only a few minutes per potential candidate to determine whether or not they meet the hiring manager's criteria. It's unr…

Post by user5994461 » Mon, Jan 27, 2020, 7:58 PM UTC

leecarraher wrote: post #13

vorpalhex wrote: post #11

Oh geez, having a team of 24 engineers across multiple countries trying to maintain a common set of bash scripts that work for 12+ unique services sounds like a disaster. Instead we have a single workflow for docker, whether it's going out to AWS or Kubernetes and all the services use an identical flow. Integration testing is a cinch since it's running actual, version matched postgres/redis/etc on the CI nodes which…

Exactly, docker standardizes something that was an otherwise nightmare to maintain across platforms and organizations. Next we need to standardize the orchestrator, my money is on kubernetes, but I wouldn't say it has won over everyone just yet.

Post by otterley » Mon, Jan 27, 2020, 8:11 PM UTC

falcolas wrote: post #62

pm90 wrote: post #55

Earlier quoted context omitted.

Using managed kubernetes solutions alleviates most of the hair pulling.

Speaking as someone using EKS: No, no it doesn't. The only thing we really handed over to someone else was the challenge of running a control plane. We still have to roll our own node images (for compliance reasons, the default images are insufficiently secure), still have to work directly with AWS to get larger etcd clusters, still have to manage the cluster itself... The trouble has barely been below the threshold…

Post by LoSboccacc » Mon, Jan 27, 2020, 9:09 PM UTC

busterarm wrote: post #90

LoSboccacc wrote: post #88

Earlier quoted context omitted.

yeah but for fighting with all the details once upfront you get an infinitely replicable environment. not just scalability but you can have as much test environments, all identical, spinning up with an apply. and the next guy in line can do it too! possibly with a convenient front-end and little understanding, so you can spend your skills elsewhere not for everyone, sure, but then which tool is?

I had that with terraform before Kubernetes anyway.

Post by blaser-waffle » Mon, Jan 27, 2020, 9:39 PM UTC

otterley wrote: post #95

falcolas wrote: post #62

Earlier quoted context omitted.

Speaking as someone using EKS: No, no it doesn't. The only thing we really handed over to someone else was the challenge of running a control plane. We still have to roll our own node images (for compliance reasons, the default images are insufficiently secure), still have to work directly with AWS to get larger etcd clusters, still have to manage the cluster itself... The trouble has barely been below the threshold…

Out of curiosity, have you considered using ECS instead? If not, why not? (Disclaimer: I work for AWS as a specialist solutions architect.)