DevOps

## Breaking Down the Wall Between Development and Operations In traditional software development, a division of labor was common: the development team wrote the code, and the operations team deployed it to the production environment. The problem lies in the "wall" this division creates. The development side wants to ship new features quickly; the operations side wants to maintain stability. Their interests conflict, and friction arises with every release. DevOps tears down this wall. Developers become mindful of operations, and operations staff get involved in the development process. The essence of DevOps is building a culture where both sides share the same goal——"deliver value to users quickly, and fix problems quickly when they arise." ## Concrete Practices **CI/CD (Continuous Integration / Continuous Delivery)**: A pipeline that automatically builds, tests, and deploys code changes. It frees teams from the anxiety of manual deployments. **Infrastructure as Code (IaC)**: Managing server and network configurations as code using tools like Terraform or Pulumi. The question "Who changed this server's configuration, and when?" becomes a thing of the past. **Monitoring and Observability**: Using tools like Datadog, Grafana, and OpenTelemetry to visualize system status in real time. The goal is to reduce the time from incident detection to recovery (MTTR). ## DevOps in the Age of AI As LLMs and AI agents are increasingly deployed in production, the scope of DevOps is expanding as well. Operational challenges that did not exist in traditional applications have emerged——such as model version control, autoscaling of inference servers, and A/B testing of prompts. MLOps was born out of this context, and DevSecOps integrates a security perspective into the mix.