3 ms·
Having ops teams around is essential in bigger companies but I've seen them turn into disablers instead of enablers as well. The devops movement was born out of
by jillesvangurp 8y ago
Having ops teams around is essential in bigger companies but I've seen them turn into disablers instead of enablers as well. The devops movement was born out of frustration with that inertia.
I witnessed AWS creeping into Nokia ten years ago. This did not go down well with internal ops initially. They did not realize they were part of the problem instead of the solution. They were a huge cost bottleneck and also a source of huge time delays and pointless bureaucracy.
Ultimately a lot of what they did stopped being a thing. Resources they controlled (e.g. firewalls between data centers, storage clusters, vms, etc.) were replaced by IAAS. This turned out to be magnitudes faster, cheaper, and more reliable (e.g. storage cluster outages were a regular thing).
Small organizations don't require dedicated ops teams anymore. If (dev)ops is done done well, ops is just not a full time job anymore. However, letting development teams do their own ops requires hiring people with ops skills as well as developer skills: i.e. devops people. So, not an anti pattern and it is perfectly valid to make sure that all teams have enough ops skills in the team. Also, these days I would expect senior developers to be not completely helpless doing ops. I don't expect them to like it but I do expect some rudimentary skills.
So,hiring, people with devops skills is not an anti-pattern. I'd actually argue having an ops team at all is an anti-pattern unless you are big enough to justify needing one. And if you don't have one, not hiring people with relevant skills would be a big anti pattern as well.
I've been around long enough to have seen most of what ops used to be about automated away or replaced by IAAS style deployments or otherwise no longer relevant. IMHO this is an ongoing thing and there is still a lot of non trivial stuff involved. A lot of time is still wasted on what is fundamentally tedious, repetitive, and error prone business of reinventing the same wheels over and over. It still seems way too hard to push out bog standard web applications in a way that results in responsible deployments with all the boxes ticked regarding security, ease of use, logging, auditing, etc. For me devops is a necessary evil. The less time I can spend on it the better. But the reality is that it still requires skills and time.
- asdkhadsj 8y agoOut of curiosity, any tips for companies small enough to not warrant an ops position, but also so "lean" (read: broke) that we can't too heavily rely on cloud solutions? Ie, I advocate self hosting a lot in my ~8dev team (in a real, 10 year old small company). I advocate this, because the last company I was at was the traditional startup and we blew tons of money on cloud solutions. Ie, if we needed to aggregate logs, we threw everything at papertrail, rather than managing it ourselves. This has given me a cost aversion, so I theoretically prefer self hosting when sane. Mostly for everything but actual VMs. With that said, a lot of self hosting leads to a lot of infra. I agree that hiring devs who also know ops is a good way to go (and would fit us well), but in this scenario, do you still think it's the better/best? edit: to be clear, I advocate using AWS/etc. I don't advocate using dozens of SaaS options to solve our modest needs at non-modest prices. Many SaaS solutions were designed for scales much larger than ours, self hosting seems most apt.
- eajr 8y ago(Not the OP) If cloud equates in your mind to expensive, then you were probably using the cloud wrong. Using AWS (for example) as a data-center and self hosting on EC2 can be pretty expensive compared to just getting a few dedicated boxes. The point of cloud architecture with tools like terraform are meant to be able to have resources be torn down and scaled down when they are unnecessary. You can't scale down bare metal, and you can't scale it up either automatically. If you have a consistent workload and know exactly what you need on any given day/time and for any given number of clients and can predict what you need - bare metal is honestly not a bad choice. Edit: Just realized I didn't answer your initial question in the post: A cloud architect, who comes from an engineering background, is more along the lines of what you would need versus just a pure ops person. My last company was a small company (startup mentality) and as chief architect I was able to design our cloud architecture as well as write code on our projects when my developers were struggling to meet deadlines.
- depr 8y agoSo what the 8 devs really need is a cloud architect?
- asdkhadsj 8y agoI think there's a miscommunication here, but I probably should have said SaaS rather than "cloud". Ie, I don't advocate self managing hardware. That's a difficult problem, one more cheaply and easily solved by using AWS, GC, etc. Yet, there are dozens of SaaS options for so many little problem you could have, and they can bleed you dry. A balance is needed. I mentioned in my original post that I advocated self hosting except for VMs. Ie, I promote usage of AWS/etc. I just don't think we can afford Papertrail, and the billion other SaaS pieces I used in my last company. Self hosting has been far more scalable and cheap, due to our modest needs.
- jrumbut 8y agoIn the most successful of the companies of the sort you've been describing that I've been around SaaS was kept pretty minimal. This was less a policy than a consequence of just having *nix skills or a desire to learn. Also many SaaSes have relatively serviceable self-hosted FOSS counterparts. Log management in particular is really a shell script/self hosted app kind of task, just share the money saved on Papertrail with the team and I'm sure they'll get on board.
- Thaxll 8y agoExcept that all those IAAS solutions must be setup / manage by ops / devops, regular dev have no clue about architecture, infrastructure as code, security, backup, alerting, best practices ect ... I have yet to see a dev with good ops skills. DevOps are not dev that moved into ops world it's quite the opposite. It's Ops people that moved into dev teams. The other thing is also that dev usually don't want to do that, and when you force a dev to do ops things it gets very dangerous.
- fxsx 8y ago"Small organizations don't require dedicated ops teams anymore" So who's gonna deploy the developers' applications and implement the necessary infrastructure for that application? Who's gonna create, maintain, and administer the CI/CD pipelines which allow us to do testing, receive feedback loops, and rollback when code does not work? Who's gonna be the guy, or team of people, who has knowledge of all the different services and architecture of all these IAAS? And then who's gonna know how to implement that?
- jillesvangurp 8y agoWhoever steps up in a team to do it. I've seen all of that built in small development teams and I've seen big companies making a mess of this. It's all about hiring the right people.