It creates an illusion of environment where instances are something you can just spawn without thinking and "focus on main task".
This abstraction was quite appealing for developers and other who think we don't need to understand or pay attention to infrastructure anymore.
This caused the hype, which brought many organisations to chaos and subsequent driving away from docker. However bonuses have been paid, promotions for "innovations" have been executed.
Docker is a fine thing to play with, but it should be kept few thousand miles away from production.
Personally I don't see where it can fit, however large or small organisation is.
> It creates an illusion of environment where instances are something you can just spawn without thinking and "focus on main task".
> This abstraction was quite appealing for developers and other who think we don't need to understand or pay attention to infrastructure anymore.
Right, and the problem with this line of thinking is that when it breaks, nobody in the entire org has any clue how to fix it. If you are doing something that leaves the garden path of a completely vanilla workflow, be very wary.
For example, docker does a really bad job of abstracting the network. At my old job, it was impossible to use docker while connected to the vpn via cisco AnyConnect. We also saw all sorts of weird issues where the company firewall would intermittently break docker.
We also ran into a lot of intermittent CI failures when using nvidia-docker.
This abstraction was quite appealing for developers and other who think we don't need to understand or pay attention to infrastructure anymore.
This caused the hype, which brought many organisations to chaos and subsequent driving away from docker. However bonuses have been paid, promotions for "innovations" have been executed.
Docker is a fine thing to play with, but it should be kept few thousand miles away from production.
Personally I don't see where it can fit, however large or small organisation is.