> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/es/concepts/intermediate-concepts/topology.md). # Topología La topología de Devolutions Server describe cómo se conectan el servidor web, la base de datos y las gateways, y abarca los patrones de despliegue todo en uno, dividido y DMZ. La topología en un despliegue de Devolutions Server describe cómo se organizan y conectan el servidor web, la base de datos, las puertas de enlace y los clientes. Entre los patrones habituales se incluyen las instalaciones todo en uno, los servidores web y de base de datos divididos, y los diseños que sitúan los componentes de Devolutions Gateway en una zona desmilitarizada para lograr un acceso remoto seguro. Comprender su topología ayuda en la planificación de la capacidad, la resolución de problemas y las revisiones de seguridad. Documentarla junto con las bóvedas y utilizar una nomenclatura coherente para los hosts y los servicios facilita que los nuevos administradores comprendan cómo circula el tráfico por el entorno. #### Temas relacionados * [Topologías](/server/es/readme/topologies.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/server/es/concepts/intermediate-concepts/topology.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 `build a script that syncs our docs to a CMS` 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.