DevOps uses a capability model, not a maturity model

Re:DevOps uses a capability model, not a maturity model by zug_zug on Thursday April 06, 2023 @08:27AM (#35467425)

This isn't unique to devops, this is a general software thing. But there is an answer, which is the standard technology stack:

- AWS - Postgres - Linux - Docker - Jenkins or similar - Slack - Pagerduty - Jira - Packer - Terraform - etc

If you stay on the path there will be dozens of tools, plugins, and paths to do outstanding things with minimal work. Parallelising builds for example is built in to jenkins (if you define the workflow), which will autoscale workers in a setup that takes < 1 hr to setup in aws.

If you're writing code to solve a problem that a standard tool exists for, you're the problem.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by samsquire on Thursday April 06, 2023 @08:46AM (#35467626)

Kind of rude but parallelising builds was referring to the work that Uber did with their monorepo setup due to all their microservices.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by chatmasta on Thursday April 06, 2023 @10:25AM (#35468679)

< 1 hr to setup Jenkins, nevermind with auto-scaling workers on AWS, is an obscene underestimate.

You'll probably spend at least an hour figuring out IAM permissions before you even get to deploy a VM.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by ilyt on Thursday April 06, 2023 @11:09AM (#35469374)

nah just throw few layers of abstraction and throw a templated YAML at another tool that sets it all up for you!

Something broke ? Well, rip it up and reinstall! But what about the data ? Who cares?

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by zug_zug on Thursday April 06, 2023 @11:46AM (#35470020)

Well, you will certainly the first time sure. But in your next 3 jobs it should be much easier.

[ Parent | on HN ]