> 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/deployment.md). # Deployment The process of making a software application available for use. Deployment is the process of releasing a software application or update into an environment where it becomes available to users. This includes activities such as building the application, transferring artifacts to servers or cloud platforms, running database migrations, and configuring networking and DNS. Deployment strategies vary in complexity and risk. Common approaches include rolling deployments (gradually replacing instances), blue-green deployments (switching traffic between two identical environments), and canary deployments (routing a small percentage of traffic to the new version before full rollout). Each strategy offers different trade-offs between speed, safety, and resource usage. In serverless architectures, deployment is simplified because there are no servers to provision or maintain. Deploying a Cloudflare Worker, for example, involves pushing code and configuration to the platform, which handles distribution to edge nodes globally. API gateway configurations are often deployed alongside application code, with routing rules, security policies, and rate limits treated as part of the deployment artifact. --- # 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/deployment.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.