3 ms·
> If I need quick hot fix RIGHT NOW, I can't just log in, change couple of lines and restart, must go through full deploy cycle. If you have the need for that
by polote 6y ago
> If I need quick hot fix RIGHT NOW, I can't just log in, change couple of lines and restart, must go through full deploy cycle.
If you have the need for that kind of thing, I don't know why you would use containers.
Containers is for organizations who have processes.
Unfortunately nowadays we teach every developer to have containers, ci/cd, terraform, test coverage, ... as a requirement
- deleted 6y ago[deleted]
- WJW 6y agoLogging in to fix something RIGHT NOW also really falls off as soon as you hit moderate scale and have to do the editing on 20-30 boxes.
- smcleod 6y agoWho really did that though? I’m sure a few. But mostly back in the days before we (almost) all had containers we automated that stuff with puppet etc... It worked ok but it had its own problems, we iterated and move on to disposable workloads and infrastructure - which has a completely different set of problems. Amongst other things it makes scaling even easier - if you need it and if you do it right. Before automation frameworks and services we had scripts, which were either nice and simple but limited, or a huge mess and highly complex (and often fragile). Before that we either had mainframes / centralised computing or we didn’t have scale. Maybe it was different in the windows world, but that’s pretty much what my experience has been across many clients over the past 16~ years with Linux/BSD etc...
- fulafel 6y agoYou can both have processes, and rare exceptions to processes. Abd even processes for exceptions (eg checklist that includes documenting what you did and reimplementing the change eg in vc'd ansible)