3 ms·
The popularity of docker in corporate environments is mostly because it allows developer teams to control the OS without dealing with sysadmins that are in a se
by tyingq 9y ago
The popularity of docker in corporate environments is mostly because it allows developer teams to control the OS without dealing with sysadmins that are in a separate organization. Similar for cloud in general.
I think many people don't see that a lot of the popularity is less about technology, and more about politics. "Devops", in general, is basically an organization change to move sysadmin's duties into the development team's domain. It has predictable upsides, and downsides.
- cookiecaper 9y agoYes, microservices and containers are a way for developers to feel important and grant cover to an unabashed manifestation of Conway's Law. This particular fad is wreaking ridiculous havoc that is going to have the computing world in quite a mess soon. In the real world, distributed systems are a complication that is better left alone if they're not necessary for a problem space. You very likely don't need Kubernetes (watch out, this sentiment will get your HN account throttled; I've already been punished for it so it's safe for me to say). The reason Google et al push these distributed systems is because it gets you to buy more cloud instances. Very predictable and straightforward behavior there. Like all technology that proliferates, this is definitely more about politics than merit, but it doesn't really move the duties around practically; anyone who thinks that a group so undisciplined and lackluster as your average software developer will willingly take on new responsibilities is detached. As a sysadmin, you just get developers delivering garbage to your doorstep and expecting you to deal with it, same as always. It's just packaged in a stupid way now, that makes the developers say "Well I sent you a container, so this should be up and running in like, 5 minutes, right?" In practice, most developers won't even write their own Dockerfiles; my experience has been that they develop locally as they always have, and then expect the sysadmins/"devops" (now a term for sysadmins) to do all that mumbo-jumbo. But yes, we've been through this song and dance before. It's static v. dynamic linking. It's shared tenancy v. single tenancy. None of it is new, it just gets a different name and oscillates from position A to position B. It's an embarrassment and a testament against our industry that we continue to thrash wildly and be so thoroughly dominated by fads.
- _jal 9y agoLooks like someone else has been around the block a couple times. There are going to be massive opportunities for good consultants in this muddle. I'm currently watching one train wreck, thankfully at a distance. Nothing novel - they moved ops under the engineering umbrella. The engineering manager not only has no clue what the differences in managing the two are, but seems unaware that there are any. So of course the good system people quickly left, the engineers are slowly discovering that containers don't magically erase the need for understanding how things work, and they're spending six figures a month on K8s consultants. We seem to have a generational cycle on IT/sysadmin/ops hate. As you get older, it becomes amusing watching every new batch of engineers learn why they exist.
- devonkim 9y agoThis kind of cycle is part of why I’m regretting 13+ years in different incarnations of ops. Developers have always gotten business priority over ops unless it comes to security and I’ve seen far more places brush aside even security in the name of more features than should be healthy to one’s sanity. Even at the peak of ops when everyone was scrambling to get security engineers and such, I simply never heard of some bright kid graduating from school and getting $200k+ comp packages... for being in ops, even for DoD cyber security BS. Ops is a cost center even in the cutting edge of organizations in this respect. Few companies will make more money by throwing more money at ops that is. Combined with the serious health hazards of being on-call I’m a bit worried when I hear about companies asking their developers to get more involved with ops.
- cookiecaper 9y agoYeah. "DevOps" originated as a naive attempt to fix this issue by eliminating the "wall" between the roles, but it was quickly misunderstood. The old-school, master of the universe-style sysadmin who had to use advanced wizardry developed out of deep knowledge and intuition about how the computer worked at a fundamental level is still the ideal developer OR operator. But it's hard to find people who even understand this role, let alone people who are hiring for it. People only seem to understand pigeonholes, despite occasional well-intended attempts to unify, that generally have disastrous results. You just need a special breed to get someone who can really function up and down the stack, and every company should seek out, train, and develop such highly-empowered "tech special forces", for lack of a better term. It's tragic that so many companies don't realize this.
- emddudley 9y ago> it allows developer teams to control the OS without dealing with sysadmins Isn't this the way it should be, to some extent? Developers make the "what" and "how" decisions for the application, sysadmins make them for the environment. Containers provide a clean separation of responsibilities. Decision-making and implementation are aligned with the feedback and results.
- orev 9y agoExcept that developers usually either don't care about the underlying issues of managing the OS, or don't have the skillset. They are focused on developing the product/features, not on ensuring that images have security patches, or even if the environment is secure is any way (file permissions, network ports, etc...). Those issues are large enough that they require dedicated resources (evidenced by the existence of professions in Operations), and moving them to a container generally just allows developers to ignore them -- not to take over the responsibility.