DevOps

Code, Deploy, Repeat.

Imagine a development model that is iterative, delivers change quickly, and that everyone in the business understands. That's the promise of DevOps: a broadly agreed approach to solution development, regardless of technology. 

Driven by workflow requirements, development processes look at the whole stack:

• Containers & other runtime requirements (Docker, LXC, VMs, pipeline actions)

• Scaling management (Kubernetes, Swarm, GKE, etc)

• Monitoring (Prometheus, Grafana, et al.)

• Glue logic (Bash, Python, CI/CD)

The benefits (and potential drawbacks) of DevOps have been argued for some years now. While still the vogue development model, DevOps' principle barrier to entry is the required scale of service delivery.

For example, if a service is likely to need a small team, the process overhead of a full DevOps model might outweigh the benefit, presenting cost and potential delay, while adhering to process. But, when services scale, details scale too. More eyes are needed.