> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/d/devops.md). # DevOps A set of practices that combines software development (Dev) and IT operations (Ops) to shorten the system development life cycle and provide continuous delivery with high software quality. DevOps is a set of practices, cultural philosophies, and tools that combines software development and IT operations to improve the speed, quality, and reliability of software delivery. DevOps emphasizes automation, collaboration between development and operations teams, continuous integration and delivery, and infrastructure as code. Key DevOps practices include automated testing, continuous deployment pipelines, monitoring and observability, incident management, and version-controlled infrastructure. Tools commonly associated with DevOps include Docker, Kubernetes, Terraform, Ansible, and CI/CD platforms like GitHub Actions and Jenkins. In API and serverless environments, DevOps practices ensure that API gateway configurations, serverless functions, and backend services are deployed consistently and reliably. Infrastructure as code allows teams to define gateway routing rules, rate limits, and security policies in version-controlled files. Monitoring and alerting provide visibility into API performance, error rates, and usage patterns, enabling rapid response to issues. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/d/devops.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.